Carbon Manufacturing Operations
Plan materials, run shop-floor work, and manage quality and costs in one manufacturing system.
- Source repo
- crbnos/carbon
- Stars
- ★ 2.8k
- Last updated
- today
- License
- NOASSERTION
- Primary language
- TypeScript
- FA score
- 60/100 · Some gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformOpenAI API · Claude API (Partial support)
- Cost
- Free tier plus a paid hosted plan
- Setup effort
- High · needs real infrastructure
- You'll need
- Typical use
- A contract manufacturer links quotes, sales orders, production jobs, and invoices while checking actual job costs.
- Not a fit if
- Teams that only need a lightweight inventory tracker
- Teams unwilling to deploy or maintain database and application services
- Website
- carbon.ms ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-10+3.3 ★/day over 7 days
- Source review
- 60/100 · Some gaps
What does this agent do, and when should you use it?
Carbon brings ERP, MRP, MES, and QMS into one Postgres database, covering quotes, orders, purchasing, inventory, planning, shop-floor execution, quality, and accounting. Engineering, planning, production, and quality share records, including multi-level BOMs, revisions, routings, and forward and backward lot and serial traceability. Users work through React Router apps, call the permission-checked REST API, or let AI clients use the same manufacturing operations through MCP. Carbon Cloud manages the application, database, updates, and backups; self-hosting is supported in a VPC, on premises, or in an air-gapped environment. It is aimed at manufacturers connecting complex assembly or high-mix, low-volume workflows, and local development requires Docker, Node.js 22, and pnpm.
Carbon stores quotes, sales orders, purchasing, inventory, BOMs, routings, planning, jobs, inspections, and accounting records in a shared Postgres system. MRP and scheduling handle demand, supply, and finite-capacity planning; MES provides digital travelers, operator terminals, 3D instructions, barcode capture, and labor capture. Quality workflows cover inspections, FAI, nonconformance, CAPA, calibration, and risk management, while traceability follows lots and serials in both directions. The application uses the same manufacturing operations exposed through POST /api/v1/{module}/{operation} and MCP tools; access follows the API key or signed-in user's permissions. A self-hosting developer can run the local Docker backend and ERP/MES apps, or use the managed Carbon Cloud service.
- A contract manufacturer links quotes, sales orders, production jobs, and invoices while checking actual job costs.
- Engineering and production teams manage multi-level BOMs, revisions, change orders, and product configurations without re-keying them across systems.
- Planners use demand, supply, routings, and finite-capacity scheduling to plan work and spot material shortages.
- Shop-floor supervisors assign digital travelers on tablets and support operators with barcode capture, labor capture, and 3D work instructions.
- Quality teams record first article inspections, nonconformances, CAPA, and calibration, then trace affected lots or serials.
- Teams that want AI clients to perform permission-scoped manufacturing operations connect to Carbon's MCP server.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Environment variables
CARBON_API_KEY- Config files
.env.example.env- Runtime
- Node.js 22
- Install notes cover
- Docker
How do you install or deploy this agent?
Choose a Carbon Cloud trial or start the full development stack locally as documented in the repository. Production self-hosting is supported in a VPC, on premises, or in an air-gapped environment; consult the project's self-hosting deployment guide for production configuration.
Local development requires Docker, Node.js 22, and pnpm via Corepack. The documented startup steps are:
git clone https://github.com/crbnos/carbon.git && cd carbon
corepack enable && pnpm install
cp .env.example .env
pnpm devHow do you use this agent?
After the development stack starts, open the ERP at http://localhost:3000 or MES at http://localhost:3001. The seeded local user is [email protected], and the dev stack skips the magic link. Populate a demo dataset with:
pnpm db:seed:dev -- --email [email protected] --dataset satelliteThe API and MCP expose the same manufacturing operations and permissions. Create an API key, then make a first request:
curl -X POST https://app.carbon.ms/api/v1/sales/getSalesOrders \
-H "Authorization: Bearer $CARBON_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "args": { "limit": 10 } }'Self-hosted instances serve the API at /api/v1. An MCP client can connect to the hosted or local MCP service; available tools are scoped to the API key or signed-in user. The README says API keys and MCP are included with Business and Enterprise plans, and using them in a self-hosted deployment requires a commercial license.
What are this agent's strengths and limitations?
- ERP, MRP, MES, and QMS share one Postgres database, avoiding synchronization jobs between separate product databases.
- The product spans multi-level BOMs, revisions, finite-capacity scheduling, shop-floor execution, quality workflows, and two-way lot/serial traceability for complex assembly and high-mix, low-volume production.
- REST API and MCP use the same operations and identity permissions, with scoped API keys or signed-in user access.
- Teams can choose managed Carbon Cloud or deploy in a VPC, on premises, or air-gapped.
- The local full stack requires Docker, Node.js 22, pnpm, and several backend services, so setup and operations are substantial.
- Hosted API keys and MCP are tied to Business and Enterprise plans; using them in a self-hosted deployment requires a commercial license.
- The repository uses an open-core license model:
packages/eeand files containing.ee.in their names are under the Carbon Commercial License rather than AGPLv3. - Its broad, manufacturing-specific scope may be excessive for teams that only need lightweight inventory tracking.
How does this agent compare with similar options?
The README presents Carbon as an open-source alternative to NetSuite, Epicor, SAP Business One, Plex, Odoo, and ERPNext, and links to comparison pages for those products.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Carbon Manufacturing Operations This agent | 60 · Some gaps | Hosted serviceFreemium | ★ 2.8k | today | TypeScript | — |
| x-use | 88 · Good | MCP serverFree | ★ 182 | 2d ago | Python | Codex · Claude Code · Claude.ai |
| OptimNow Cloud FinOps Library | 67 · Some gaps | Agent plugin / skillFree | ★ 67 | today | Python | Claude Code |
| MikroTik Router MCP | 64 · Some gaps | MCP serverFree | ★ 331 | today | Python | — |
How does FollowAgents rate this agent?
Why each dimension lost points
The README says API and MCP share identity permissions and tenant row-level security, and identifies where API keys are created. The restore guide documents a confirmation prompt, default email scrubbing, and email-sending cautions; test samples also show rejection of invalid accounting input. Dependency security is supported only by pinned versions, patch declarations, and an allowed build-script list; no audit or vulnerability response evidence appears. CI workflows have image-publishing permissions, so evidence for controlling external effects is limited. AGENTS.md provides clear project attribution, but primarily contains contributor constraints.
The README describes the local stack, API, and database architecture in detail, while test samples demonstrate rejection of invalid input and planning edge cases. However, the restore text says storage.objects is truncated by default and later describes --keep-storage-objects as retaining it; the implementation is not in the sample, so this behavior cannot be fully reconciled. Dependencies and services are identified, and the README clearly states which assembler endpoints are unavailable without that service. Tests show readable validation errors.
The product targets manufacturing and lists ERP, MRP, MES, and QMS scenarios along with API/MCP, self-hosted, cloud, and local-development options. Skills have explicit trigger descriptions, and AGENTS.md routes tasks to subsystem guidance. The packet samples only some skills and source, so it cannot establish coverage of every audience or environment need.
The README has useful navigation, architecture, stack, monorepo, installation, development, and command sections, plus examples, restore cautions, and limitations when a component is absent. LICENSE distinguishes AGPLv3, commercial-license files, and third-party components. Cargo.toml provides a version, but the sample has no user-facing changelog or clear named maintenance owner, so those criteria receive partial credit. AGENTS.md is contributor guidance rather than an end-user guide.
The product brings manufacturing execution, planning, quality, inventory, and API/MCP onto one data model. The README gives actionable local-start and API-call examples, and test samples make accounting and planning behavior concrete, supporting practical value for the intended manufacturing teams. With no execution evidence or independent material on cost savings or output quality, the scores remain conservative at 2.
README architecture and feature claims receive some corroboration from the package inventory, API exports, test samples, and license. Test code provides traceable inputs, assertions, and error messages. Some feature, security, and performance claims remain README assertions without corresponding implementation or validation in the sample, so fact/inference separation and cross-source corroboration do not earn full marks.
- This assessment uses only the supplied static sample; the skill and source sample is incomplete, and no build, installation, or runtime verification was performed.
- The restore guide's description of default storage.objects handling should be checked against the unsupplied script. Commercial licensing applies to packages/ee and files whose names contain .ee.
FAQ
Can I self-host Carbon for free?
packages/ee and files whose names contain .ee. use the Carbon Commercial License. API keys and MCP require a commercial license in a self-hosted deployment.What can an AI client do through MCP?
What infrastructure does deployment require?
Can Carbon run in an air-gapped environment?
Must I configure an external AI provider to develop locally?
Is Carbon Manufacturing Operations open source?
Is Carbon Manufacturing Operations safe to use?
Is Carbon Manufacturing Operations still maintained?
Who makes Carbon Manufacturing Operations?
What is Carbon Manufacturing Operations's official website?
Thanks — we use this to improve the page.