Three plans. One list price each.

EU instruments at EU level, the UK, US federal and priority states (California, Colorado, Illinois, Massachusetts, New York, Texas), and Australia. We are adding coverage over time. No jurisdiction is blocked on a paid plan, and there is no per-jurisdiction cap.

Neither. You pay one of three annual list prices. Which of the three fits depends on how many corporate entities you run (Foundation up to 3, Compliance Pro up to 15, Compliance Suite for 15 or more), which capabilities you want, and the level of support you need. Foundation covers three corporate entities, and the platform keeps that boundary at save time, so the number you bought is the number the workspace holds you to. Your scope page shows the count against it, upgrading lifts it in place, and every entity already on record stays there to read and to edit - a group above its capacity keeps correcting and removing companies, and what waits is adding a further one. Seats, policies, and jurisdictions are all uncapped, so bring as many reviewers into the workspace as the job needs.

Digest items link to the primary source we captured, and a Word redline is drafted against the dated copy of that source as it read on the day it was reviewed. Memos link the regulator's own text they were drafted from, and your team keeps or drops each one, with the decision written to the audit chain. Everything regSpace produces is draft intelligence for your qualified team to review and sign off.

Connectors ride with Compliance Pro and Compliance Suite. Live today: SCIM identity providers (Okta, Entra, Google Workspace, OneLogin, JumpCloud), BambooHR / Personio / HiBob, AWS, Google Cloud, Jira, and Tropic. Other integrations become available over time, and billing starts once one is live for you.

A contractual SLA is part of Compliance Suite only; Foundation and Compliance Pro are best-effort support. On SOC 2: we maintain SOC 2 control mapping in our controls library, but a formal attestation is not yet started, so we do not claim certification. Ask for the security pack and we will share exactly where we are.

Your workspace is built straight after checkout and the admin sign-in goes to the email address you enter at the till, so use a work address. The company name you give at checkout becomes your workspace name, refined during onboarding, and you can add as many colleagues as the job needs once you are in. Stripe sends the receipt. If the sign-in email has not arrived within a few minutes, email hello@regspace.ai with the address you paid with and we will sort it.

Cancel in your Stripe billing portal or tell us, and your subscription stops at the end of the term you have paid for. Your workspace and everything in it stay as they are until we have agreed with you what should happen to them, so you keep the time to export what you need. Ask and we will walk you through the export.

Yes, from the Administration page in your workspace. Where you bought through this site, Change plan opens your Stripe billing portal, which also holds your invoices and payment card; where the plan was agreed with us, the same page gives you our address and we quote the difference. Your workspace follows your subscription: a change reaches it the moment Stripe applies the change, so the capabilities and the entity capacity of the new plan arrive with it. When each change takes effect, and what it costs, is set by your billing portal's own rules and shown to you at the point you choose. Your entity capacity comes with the plan, and a group above the new capacity keeps every company on record and keeps renaming, correcting and removing them - what waits is adding a further one.

Your workspace keeps running. A declined card is recorded, we hear about it, and Stripe retries on its own schedule, with your plan, your data and every capability exactly as they were throughout. We reach out so the card can be sorted while there is time, and you can update it yourself in your Stripe billing portal from the Administration page.