Strict YAML with JSON Schemas, a validator with 107 checks, generated tables, REST, SSE and MCP. Nothing hand-wired per app.
Rangka OS gives businesses the building blocks for CRM, sales, POS and ERP as readable .rk files, and keeps adapting as the business changes.


The problem.
Stop settling for tradeoffs.
Declare apps in files, change them through reviewed proposals, run them on infrastructure you own.
Strict YAML with JSON Schemas, a validator with 107 checks, generated tables, REST, SSE and MCP. Nothing hand-wired per app.
Rangka AI reads your models and proposes change sets in layers 4–6 only. Guardrails live in code, not in a prompt.
Validated, previewed on a copy, approved by a person, applied live, reverted in one click. High-risk changes need the owner.
CRM, sales, invoicing, payments and stock ship as .rk modules and apps for Indonesian businesses: rupiah without decimals, PPN 12% on DPP 11/12, NPWP, QRIS and WhatsApp. Install one with a line in config.rk.
Browse the apps →
Ask Rangka AI for a PO number on invoices. It writes an overlay in your company layer, explains why, and shows the exact diff and risk. A person approves; the kernel applies it live and can revert it.
How change sets work →
Your business is a folder of files in your git, served by one Go binary and one Postgres. Queue, scheduler, realtime, cache and single sign-on are switched on in system.rk.
Read the architecture →


# check every .rk file against the schemas $ rangka validate --apps ../rangka-apps # DATABASE_URL points at your Postgres $ rangka migrate --apps ../rangka-apps $ rangka seed --apps ../rangka-apps --org kopi-senja # REST, SSE, MCP and Rangka ID on one port $ rangka serve --apps ../rangka-apps --addr :8080
For the people who run the business.

Compact lists, boards and forms with quick filters, pagination and skeleton loading.

⌘K finds any record or screen, or hands the question to Raka.

See the file, the lines and the SQL before anything goes live.

Numbering at submit, cancel and amend, PPN and payments, generated from the model.

Number cards, charts and lists declared in dashboard.rk and computed on open.

Apps, capabilities, connectors, members, themes and audit in the Console.
Made for Indonesia.
Example scenario
A coffee chain with three outlets wants the customer’s PO number on invoices. Raka, the Rangka AI agent, proposes a one-field overlay; the owner approves it from her phone and it is live before lunch.

Any questions?
No, it is source-available under the Elastic License 2.0 (ELv2). The code is public on GitHub and free to self-host, change and use for your own business. Offering Rangka to others as a hosted or managed service needs a separate agreement with Saga Tekno Studio. Only the hosted Rangka Cloud is closed.