Security and control for insurance data workflows

Qluster is built for controlled review, approval, and release of recurring insurance reporting data, with clear boundaries around access, auditability, deployment, and AI-assisted workflows.

Deployment model

Qluster is typically delivered as a managed cloud service.

For teams with specific infrastructure requirements, dedicated private deployments may be discussed during evaluation. Those deployments are not positioned as a standard self-managed product offering. They require clear agreement on infrastructure responsibilities, operator access, upgrade process, and support boundaries.

Access control and data isolation

Access can be scoped by organization, dataset, and source. In multi-source workflows, each row is stamped with its source so external users can be limited to their own data while internal admins retain a unified view.

• organization-level access controls
• dataset-level separation
• source-aware row-level isolation
• unified internal oversight across shared workflows

Auditability

Qluster keeps a visible record of how data moved from failure to release.

• what failed
• what changed
• who changed it
• when it changed
• what was approved
• what was promoted into reusable mappings or policies

Deterministic workflow

Qluster is designed around a predictable contract: same file in, same result out. Re-imports should not create surprise outcomes, and edits trigger rechecks only for the affected rows.

AI boundaries

Qluster can support AI-assisted workflows for drafting fixes, mappings, or starter policies, but those suggestions are not silently applied to production data. Humans review what was suggested, decide what should be approved, and control what becomes reusable logic.

Deployment and operating requirements for AI-assisted workflows may vary by customer environment and should be discussed during evaluation.

Support boundaries for private deployments

Where dedicated private deployments are considered, Qluster expects clear support and operating boundaries. Customers may manage core infrastructure components such as Kubernetes, Postgres, and object storage, while Qluster retains responsibility for application-level support, upgrades, and troubleshooting access as defined during evaluation.

The goal is to avoid pushing application debugging onto customer teams that should not need to inspect source code or interpret internal stack traces.

Security review process

We can share current security information, architecture details, and deployment considerations during evaluation. If your team requires a security review as part of procurement, contact us and we will handle it in the sales process.

Need security or deployment information for evaluation?

If your team is reviewing controls, access boundaries, auditability, or deployment requirements, contact us and we will route the conversation appropriately.