Skip to content

Carbon / Security model

The package does not have to leave the building.

Your environment. Your model. Projects that cannot see each other. Install posture, shorter, is on Security.

Request a trial

01

Customer environment only

VPC, private cloud, or on-premises. No Carbon SaaS path. If you cannot run it there, this is not a fit.

02

Your model, your contract

Azure OpenAI, Bedrock, Vertex, or an internal server. Carbon does not host inference. Rendering stays on the install.

03

Per-project isolation

A 510(k) build cannot see a FedRAMP build. Isolation is a product rule, not a switch someone has to remember.

04

Configured, not pasted

Intake sets derived defaults through a rule table. Raw answers are not dumped into every prompt. You can edit the summary before phase one.

05

Code never becomes code

Snippets constrain the specification. They are never used to generate application code. That trace is out of scope on purpose.

06

Tamper-evident export

The history log is append-only and hash-chained. If a file changes after export, one check shows it.

Not claimed

SOC 2, ISO 27001, and a BAA are not done.

They are in development. A questionnaire will get an incomplete answer until they are. Quality checks inside a package are not a company attestation. Those checks. Ask for the questionnaire.