Tell us what you are being audited against.
This starts a scoping conversation. CarcGRC is sold sales-led — there is no self-serve checkout, no plan tiers and no payment gateway anywhere in the product — so the outcome of this form is a call, not an account.
Every customer runs on their own stack — its own app, worker and database, provisioned to the signed contract. Your data does not sit in a table shared with other customers, which is also why scope has to be agreed before anything is stood up.
CarcGRC deployment model. Each customer receives a dedicated deployment: a Next.js application, a BullMQ worker, a Postgres database, a Redis queue and object storage, all provisioned for that customer alone. The deployment boundary — not a row-level policy — is what separates one customer from another.
Three steps, and none of them are a checkout.
CarcGRC is not bought through this page. It is scoped with you, written into a contract, and then provisioned as infrastructure — which is the whole reason there is no pricing page to send you to.
- 01
A conversation, not a demo script
Which frameworks you are being asked for, what you run today, who owns compliance internally, and when the audit is. We will also tell you exactly where the build stands against Phase 1 rather than showing you a customer wall we have not earned yet.
- 02
Scope written into a contract
Which frameworks, how many employees, how many integrations, how much agent capacity, how much storage. There are no plan tiers to pick from — the scope is agreed with you and then becomes your deployment’s configuration.
- 03
Your own deployment, provisioned by ops
App, background worker, Postgres, Redis and object storage, stood up for your organisation alone. License state and every entitlement cap are set on that deployment to match the signed scope. There is no in-app upgrade button, because there is nothing to upgrade to.
CarcGRC is pre-launch. Phase 1 is defined as sellable — six frameworks, the eight-agent suite, twenty integrations, the auditor portal and env-driven licensing — and its launch criterion is ten design partners running it in production. We are talking to those design partners now, and a demo today is a straight conversation about where the build stands against that list.