Pricing: healthcare and regulated
Healthcare and regulated work, reviewed first.
Healthcare, government and other regulated deployments are quoted individually after a requirements review. Nothing below is a package: it is the list of what the review covers.
Availability is subject to review and completion of required agreements and controls before protected health information is processed.
Separate infrastructure
Whether your deployment runs on infrastructure set apart from the shared Korps Cloud, and what that changes about hosting and cost.
Customer isolation
How your organisation, its data and its workers are kept apart from every other customer, at the database, network and runtime layers.
BAA and provider review
Which agreements are required between you, Korps and each AI or tool provider a worker would touch, and which providers are acceptable to you.
Approved AI processing
Which models and providers may process which categories of data, and how a worker is prevented from reaching any other.
Access controls
Who can see and do what: single sign-on, roles, approvals, device requirements and how access is granted and removed.
Audit requirements
What must be recorded, for how long, who can read it, and how it is exported. Activity already names every system a worker touched.
Operating responsibilities
Which duties stay with your organisation and which Korps takes on, written down before go-live.
Government deployments
Public-sector work has its own requirements review, covering procurement, residency and the controls your authority specifies.
Where Korps stands today
Korps states its certifications, agreements and controls with evidence on the security page, and nowhere else. HIPAA compliance and a business associate agreement are established per deployment through the requirements review, not assumed. The review is how we find out what your deployment needs and whether Korps can meet it; the honest outcome may be that it cannot yet.
How a review works
- Tell us the work. The process, the data categories involved and the systems a worker would touch.
- We map the requirements. Infrastructure, isolation, agreements, approved processing, access, audit and operating duties, against what Korps can provide today.
- You receive a written proposal or a plain no. A proposal states scope, controls, responsibilities, timeline and price. Nothing is processed before the agreements and controls it names are in place.
Questions
Is Korps HIPAA compliant?
Korps makes no such claim on this page. Whether a specific deployment can meet your obligations is what the requirements review establishes, and it is completed before any protected health information is processed.
Will Korps sign a BAA?
That is part of the review. It depends on the deployment, the providers involved and the agreements each of them requires. No BAA is represented as executed until it is.
Can workers use the AI provider we already have?
Usually the starting point. The review lists which providers and models are approved for which data, and how a worker is kept from reaching any other.
Is this the managed service?
It can be either. Regulated deployments are quoted on their own whether your team runs the system or Korps does; the review determines which controls apply in each case.