Korcado unifies ERP, CRM, subscriptions, telecom and workforce operations on a single metadata-driven platform. Every module shares one catalog, one pricing engine, and one governed source of truth.
Korcado modules aren't separate products stitched together — they're built on one shared foundation. Define a product, a price, or a business rule once, and every module uses it automatically. And because the entire spine is exposed over MCP, AI agents are first-class users of that same foundation — not a bolt-on.
One catalog and a deterministic pricing engine serve quoting, order billing, subscriptions and telecom rating. Bundles, tiers and usage-based pricing — with full calculation traceability on every amount.
Objects, fields, layouts, business rules and workflows are configuration, not code. Screen Builder renders tenant-specific UI from JSON — versioned, reviewable and portable between environments.
Client-specific logic runs as Go plugins or sandboxed WASM extensions via wazero — resource-budgeted and versioned, so custom code can't breach the core or block an upgrade.
Tenant isolation is enforced by the platform, not by application code. Role-based access reaches down to object, field and action, and every posting carries who, when and on what basis.
Business events flow through the spine, so procurement receipts, stock movements and postings react to each other without point-to-point integration.
The platform ships with a native MCP (Model Context Protocol) server: every object, action, report and workflow on the spine is addressable by AI — Korcado AI or agents you bring. Agents authenticate as principals with the same role-based permissions and tenant isolation as people, and every AI action lands on the same audit trail.
Korcado AI is not a copilot bolted beside the system — it is the operating layer on top of it. People set policy, approve exceptions and make the calls; AI carries out the recurring work, and every action lands on the same governed record as a manual one.
Chat, email, scheduled jobs and business events — where people and the business initiate work.
Assistants and governed workflows that classify documents, propose postings, draft responses and route exceptions to the right owner.
Catalog, pricing, master data, permissions and the auditable record — where integrity is enforced and evidence is kept.
| Proposed action | Routing | Evidence |
|---|---|---|
| Recognized supplier invoice | Within policy — executes automatically | Posting trace linked to the source document |
| New vendor or customer | Waits for master-data approval | Checks performed and the proposed record |
| High-value adjustment | Requires the approvals your policy defines | Preview, rationale and who signed off |
Every AI action is dry-run, risk-routed and recorded · an assistant never posts alone
Modular, multi-tenant business applications with Korcado AI built into every module, on an extensible plugin architecture. Adopt what the business needs now, then extend without creating a new silo later.
Purchase orders, goods receipt, AI-assisted three-way matching, QC routing and supplier management — driven by events on the spine, not batch syncs.
Multi-location inventory, bin management, stock transfers and AI-driven demand forecasting on a real-time stock position — the same numbers finance closes from.
Production orders, bills of material, material traceability and costing, with AI-assisted planning and shop-floor visibility — on the same record finance closes from.
Chart of accounts, GL, AP/AR and a multi-currency ledger with AI-assisted classification and posting, and tax support for all regions — VAT, GST and sales tax. Every posting traceable back to its source transaction.
Employee records, organisation structure, roles and leave, with AI on hand for drafting and policy questions — the single source of people data every other module reads from.
AI-assisted scheduling, attendance and shift capture, and time tracking from the floor and the field — written straight to the governed spine.
Plugin engine with native Go plugins and sandboxed WASM extensions via wazero — callable by AI agents over MCP. Build custom modules without touching, or forking, the core.
JSON-driven UI renderer with a drag-and-drop, AI-assisted layout builder. Create tenant-specific screens without code, and carry them safely through upgrades.
Configurable foundations with the operational depth each sector actually needs.
Production control, material traceability, costing and shop-floor visibility on the same record finance closes from.
Network inventory, fulfilment sequencing, route tracking and service-level visibility.
Subscriptions, entitlements and consumption billing pinned to the same pricing engine as one-time sales.
Quote to delivery to invoice, with utilisation and service context on one customer record.
Attendance, capture and approvals from the floor and the field — flowing straight into the same system the office runs on.
Plenty of suites promise integration. Korcado is different by construction — and the difference compounds as you grow.
One catalog, one pricing engine, one ledger shared by every module. The quote, the invoice and the report always agree — so month-end is a review, not an investigation.
Objects, screens, rules and workflows are metadata, not custom code. Adapt the system in days, and carry every change safely through upgrades.
A native MCP server makes AI a first-class user of the platform. Agents work under the same permissions and audit trail as people — assistance without new risk.
Client-specific logic runs in sandboxed, resource-budgeted extensions that can't breach the core or hold a release hostage.
Multi-tenant isolation, role-based access down to the field, and a complete audit trail on every posting — built into the platform, not bolted on per project.
One-time sales, subscriptions and usage-based billing priced by the same deterministic engine, with full calculation traceability behind every amount.
| A stitched stack | With Korcado | |
|---|---|---|
| Product & price definition | Re-keyed in every system; quotes and invoices drift apart | Defined once in the unified catalog and used everywhere |
| Order to cash | Hand-offs between systems, reconciled after the fact | One record moves from order to receipt to invoice |
| Client-specific logic | Forks the codebase and blocks future releases | Sandboxed, budgeted extensions that can't breach the core |
| Change requests | Custom code per integration, re-tested on every upgrade | Objects, layouts and workflows configured — upgrade-safe |
| Multi-tenancy | Bolted on per application, verified per release | Isolation enforced by the platform itself |
One platform to buy, one to learn, one to secure · one version of the truth to run on
Control is a property of the platform, not a layer each project has to add.
Role-based access down to object, field and action, applied consistently across every module.
Every posting carries who, when and on what basis, so period close is a review rather than a reconstruction.
Tenant data separation enforced by the platform, not by application code.
Extensions run sandboxed and resource-budgeted; client logic can't compromise platform integrity.
Objects, layouts and workflows are metadata — versioned, reviewable and portable between environments.
Allocation evidence and full calculation traceability carried with the transaction, not assembled at period close.