Skip to content

The business OS
your AI can safely change

Rangka OS gives businesses the building blocks for CRM, sales, POS and ERP as readable .rk files, and keeps adapting as the business changes.

Rangka
Rangka CRM dashboard generated from .rk filesRangka CRM dashboard in dark mode
Built on
  • PostgreSQL
  • Go
  • React
  • OpenID Connect
  • MCP
  • JSON Schema
+ Architecture

The problem.

Business software gives you an edge, but fitting it to your business comes with tradeoffs

Off-the-shelf apps
You bend the shop to the software. A missing field becomes a spreadsheet on the side, and the real process lives in WhatsApp.
Custom builds
Version one ships, then every change waits for a developer and risks breaking something nobody remembers writing.

Stop settling for tradeoffs.

Assemble, change and own your business apps, with AI that asks first

Declare apps in files, change them through reviewed proposals, run them on infrastructure you own.

Production-grade core

Strict YAML with JSON Schemas, a validator with 107 checks, generated tables, REST, SSE and MCP. Nothing hand-wired per app.

Concept.rk files→
AI for rapid changes

Rangka AI reads your models and proposes change sets in layers 4–6 only. Guardrails live in code, not in a prompt.

ToolRangka AI→
Control without drag

Validated, previewed on a copy, approved by a person, applied live, reverted in one click. High-risk changes need the owner.

ConceptChange sets→

Start with
ready-made business apps

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 →

Change it
without an engineer

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 →

Stay in control with
self-hosted infrastructure

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 →
Start with ready-made business apps
Change it without an engineer
# 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.

Give your team apps they’ll actually use

Familiar, modern interface

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

Search and ask in one place

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

Every change is a diff

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

Documents that behave

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

Dashboards from files

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

A control pane for owners

Apps, capabilities, connectors, members, themes and audit in the Console.

Made for Indonesia.

Built for how
Indonesian businesses run

  • RpRupiah without decimals
  • 12%PPN on DPP 11/12
  • QRISand WhatsApp connectors
  • IDBahasa Indonesia first
1/3

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.
Kopi SenjaDemo company in rangka-apps

Any questions?

Stop bending your business.
Start building, with Rangka

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.

Not yet. Rangka OS is in alpha (v0.5.0-alpha): it runs end to end, backs up and restores, enforces permissions and row scope, and is being readied for the first pilot businesses. The CEL engine, YAML reader, JSON Schema validator, router and job queue are still small in-tree packages that will be swapped for the upstream libraries; see the roadmap.

No for apps: models, rules, screens and dashboards are .rk files, changed by owners or Rangka AI through change sets. Yes if you want to work on the Go kernel.

AI can only propose. Every change set is validated, previewed on a copy with its SQL, and approved by a person; high-risk changes need the owner. Applied changes can be reverted.

Yes. One Go binary and one Postgres run everything, including the queue, scheduler, realtime and cache.

Apps are plain files with schemas rather than code modules, changes are reviewable diffs, and AI is a guarded, first-class way to change them.