Carbon

Self-hosted ERP on your infrastructure

Deploy ERP, MRP, MES and QMS in your cloud account, on-prem or air-gapped. Keep the application and Postgres data inside a boundary you control.

Carbon running on your own servers
Carbon running on your own servers
CMMC · NIST 800-171
Keep CUI in your security boundary
Run Carbon inside infrastructure you control. Enterprise BYOC includes deployment-specific inputs for your SSP, POA&M and SPRS score.
Data ownership
Store records in your database
BOMs, travelers, serial genealogy and costs remain in a Postgres database in your account or network.
Complete control
Control the complete deployment
Set the network, encryption keys, identity provider, AI models, backup policy and retention rules.

Hard tech unicorns build on Carbon.

And some of the world's most innovative manufacturers
MinimalKformSygnalRoboRen-TeqDigital MetalZeroWitty MachinesAnvilAllinol TechnologiesSaekiBlack Cat LabsM3 Aerospace
Bring your own cloud

Your cloud account, operated by Carbon.

BYOC deploys Carbon into your cloud account. We operate releases, certificates and monitoring while you retain control of the account, network and data.

Rearden/Overview
2 envs
Rearden Metal
rearden · ws_01m33172zmemdb6ya43jnz9bwx
Environments
2all applied
Awaiting approval
1
Running
0
Seats
48of 60 licensed
Environments
Environment
Release
staging
rearden-staging
0.2.18
prod
rearden-prod
0.2.22
Provisioning
Provision environments on demand
Connect your cloud account, choose a region and deploy an isolated environment for staging, production or a specific site.
Forks
Deploy your own fork
Build and release a customized Carbon fork through the same staging and production pipeline as the standard distribution.
Single-tenant
Single-tenant by design
Each deployment has its own application, database and object storage in your cloud account. Application data is not copied into Carbon's managed cloud.
CMMC · NIST 800-171

Keep CUI inside your security boundary.

Self-host Carbon to keep production records and CUI in infrastructure you control. Enterprise BYOC deployments include system-specific inputs for your SSP, POA&M and SPRS score.

Data residency
Keep production data in your environment
Run Carbon against Postgres in your VPC, data center or isolated network. BOMs, travelers, genealogy and costs stay inside that boundary.
Open source
Review the code before deployment
Inspect the application on GitHub, run your security review and extend the AGPL-3.0 Community edition for your process.
White-glove
Deployment and migration support
Enterprise engagements can include architecture, installation, legacy data migration, training and an SLA.
Multi-entity · Multi-location

Run every site on one ledger.

Manage one facility or multiple entities and locations from Postgres inside your perimeter. Configure currency, chart of accounts and tax by entity, then consolidate reporting and inter-site transfers.

→ Multi-entity accounting with intercompany transactions
→ Consolidated books across every location you run
→ One schema, one backup, one system to secure
Rearden MetalUSDEliminationUSDRearden SteelUSDd’Anconia CopperARSEliminationUSDRearden OreUSD
4 entities · 2 currencies · one ledger
Quality & traceability

Keep traceability inside your network.

Open any serial number to see its material certificates, operators, measurements and deviations. First articles, NCRs, CAPAs and calibrations link to the same production records.

→ Serial and lot genealogy, forwards and back
→ NCR to CAPA workflow with sign-off
→ Certificates generated from your own live data
Quality / traceability record
Quality / traceability record
Manufacturing execution

Run the shop floor on your servers.

Serve digital travelers, operator terminals, barcode tracking and finite-capacity schedules from the Carbon instance you host. Production does not depend on Carbon's managed cloud.

→ Digital travelers with work instructions
→ QR and barcode tracking on every unit
→ Finite capacity scheduling that reacts
Shop floor / job traveler
Shop floor / job traveler
Deploy it your way

One codebase across every deployment model.

Run the same application on one Docker host, a private cloud cluster or an isolated on-prem network.

01
Managed BYOC
Carbon deploys into your cloud account and operates upgrades, certificates and monitoring. Application data remains in your account.
02
Docker
Run the application, API and MCP server in containers with Postgres. Start on one host, then move to a clustered deployment.
03
Self-managed cloud
Operate Carbon in your AWS, Google Cloud or Azure VPC with managed Postgres. You manage the network, keys, backups and releases.
04
On-prem & air-gapped
Operate without outbound calls inside an isolated network. Air-gapped deployment and licensing are Enterprise features.
# Clone the source and bring up the whole stack
git clone https://github.com/crbnos/carbon.git
cd carbon
docker compose up -d

# App, API, MCP server and Postgres — all on your box.

→ Full deployment guides live in the documentation.

Your stack, top to bottom

Control the data, models and storage.

Postgres
One database for every module
ERP, MRP, MES and QMS share a Postgres schema with row-level security. There are no synchronization jobs between separate product databases.
Your LLM
Connect your own AI models
Use the REST API and built-in MCP server with hosted or local models. Requests stay inside your deployment and use Carbon permissions. Self-hosted API keys and MCP require a commercial license.
Your storage
Store files in your object storage
Keep attachments, drawings and certificates in object storage you control, protected by signed URLs and application access rules.

Use the same product in every environment.

Managed cloud and self-hosted Carbon use the same codebase. The Community edition is available under AGPL-3.0; a commercial license unlocks Enterprise features for self-hosted deployments.

  • ERP — quotes, orders, purchasing, inventory and job costing
  • MRP — demand, supply planning, BOM and routing versions
  • MES — digital travelers, operator terminal, live scheduling
  • QMS — first article, NCR/CAPA, calibration and genealogy
  • REST API and MCP server across every module (commercial license to self-host)
  • SSO / SAML, granular permissions and row-level security
  • Multi-entity, multi-location, consolidated accounting
  • ITAR-ready, CMMC and NIST 800-171 aligned deployment
Part configurator / BOM tree
Part configurator / BOM tree
Open source core

Inspect, deploy and extend the source.

Carbon is a TypeScript monorepo backed by Postgres. Self-host the Community edition under AGPL-3.0, or use a commercial license for Enterprise modules and air-gapped deployments. Review the code against your security requirements before rollout.

TypeScriptReactPostgresRLSDockerREST + MCPAGPL-3.0 core

Common questions.

Is Carbon open source?

Yes. The Community edition includes the core ERP, MRP, MES and QMS and is available on GitHub under AGPL-3.0. Enterprise features and alternative licensing require a commercial agreement.

How does Carbon support CMMC requirements?

Self-hosting keeps CUI inside an infrastructure boundary you control. For Enterprise BYOC deployments, we provide deployment-specific inputs for your System Security Plan, POA&M and SPRS score. Your organization remains responsible for its full CMMC program and assessment.

Can Carbon run fully air-gapped?

Yes. With an Enterprise license, Carbon runs in a restricted network without outbound calls. The application is containerized and uses a Postgres database you control.

What is bring-your-own-cloud (BYOC)?

BYOC is managed self-hosting. Carbon deploys the application and data services into your cloud account, then operates releases, certificates and monitoring through a control plane. You approve upgrades and retain control of the infrastructure and data.

Is the self-hosted version the same as the cloud?

Yes. Managed cloud and self-hosted deployments use the same codebase. The Community edition includes core manufacturing functions; the REST API, MCP server and other Enterprise features require a commercial license when self-hosted.

Can I bring my own AI models?

Yes. Connect hosted or local models through Carbon's REST API and built-in MCP server. Both use Carbon identities and permissions. Self-hosted API keys and MCP access require a commercial license.

Do you help with deployment?

Yes. BYOC includes deployment and operations in your cloud account. Enterprise engagements can also include data migration, custom integrations, training and an SLA.

Choose your deployment model

Your factory. Your servers.

Deploy the Community edition yourself or work with our team on BYOC, on-prem and air-gapped Enterprise deployments.