Your CRM's Acme and your invoice's Acme are the same row
emko cloud is a business operating system for companies that outgrew the spreadsheet and can't stomach an ERP. Sales, orders, inventory, products, projects, hiring, learning and a B2B marketplace — nine domains, one set of records, one process to run.
Not nine integrated apps. One system where nine business areas share the same data.
One record per person. One record per company. Everywhere.
A person is one record whether they appear as a project manager, a call participant, a story assignee, a warehouse contact or an employee. An account is one record whether it's a lead's employer, an invoice's buyer or a marketplace vendor.
Nothing to sync. No integration to maintain. No meeting about which system is right.
- Your CRM contact, your project manager and your employee are the same person — not three rows you keep in step.
- Login and human identity are separate on purpose: a person can exist without a login, and a login is revocable without deleting the person.
- Teams and projects aren't labels. They're permission scopes the whole system understands.
- Custom fields on people, defined by you, without waiting for a release.
- Every company record carries what you actually file: tax ID, industry, revenue band, billing and shipping addresses.
From quote to cash, without re-keying anything
One chain, end to end. Each step carries the last one forward.
| Step | What happens | Where it lands |
|---|---|---|
| Lead | Someone shows interest | CRM |
| Opportunity | The deal gets a value, a stage and an owner | CRM |
| Quote | A priced proposal with a validity date | Orders |
| Order | The customer confirms; line items carry over | Orders |
| Receiving | The order creates the physical units in your warehouse | Warehouse |
| Invoice | Built from the confirmed order, covering those exact units | Orders |
The quote that won the deal stays linked to the deal, and becomes the order, and becomes the invoice. Close a deal and you get a record, not a label.
Nine domains, one spine
| Code | Module | What it runs |
|---|---|---|
| CORE | Identity & org | People, companies, users, teams, projects, and a built-in CMS |
| OMS | Orders | Price books, quotes, orders, invoices, rentals, reservations |
| WMS | Warehouse | Warehouses, individual units, stocktakes |
| PIM | Products | Products, variants, brands, media |
| MP | Marketplace | Multi-vendor B2B catalogue, carts, contract pricing |
| CRM | Sales | Leads, opportunities, contacts, calls, emails, meetings |
| APM | Projects | Backlogs, stories, tasks, team planning |
| LMS | Learning | Courses as maps, not playlists |
| ATS | Hiring | Project positions, vacancies, scored candidates |
Plus notes, tags and content that work on every record in every module — one commenting system, not nine.
Every operation is already an AI tool
Most products bolt a chatbot on afterwards. Here the assistant speaks the system's native language, because every business operation is exposed as a tool the moment it exists.
- It runs under your permissions. The assistant literally cannot see or do anything you can't. Same check, same code path, no exceptions.
- It reads the same screens you do. Every page in the product has a Markdown twin. The assistant reads that — not a scraped approximation of your UI.
- It asks before it breaks things. Destructive actions get confirmed in plain words. It reads before it writes. It never routes around a permission denial — it tells you it was denied and stops.
- Its instructions are a file you can edit. Change how the assistant behaves without waiting for a release.
Tenancy isn't a filter someone remembered to write
Your data is isolated one layer below the business logic. Every read, list, count, update and delete is scoped to your tenant at the data layer, so no feature — existing or future, ours or yours — can reach across the boundary even if it tries.
- Permissions are grants, not job titles. A "Sales Manager" at one company holds a different set of powers than a "Sales Manager" at another. You grant the actual permissions, scoped by company, team, project, record, status or time window.
- Nothing is hard-deleted. Deletes are reversible and cascades are explicit.
- Everything is logged. Every operation is recorded with who, when, what went in and what came out.
One process. Your server, or ours.
No separate frontend server. No bundler running in production. No container orchestra. emko cloud is one process with a database behind it — SQLite to start, Postgres when you outgrow it.
Required configuration is two values. Run it on your own hardware, in your own jurisdiction, with your data on your disk — or let us run it for you.
Start where it hurts most
Bring in the module that's costing you time this quarter. The rest is already there when you need it, sharing the same people, the same companies and the same permissions.