Skip to content

System capabilities ​

The hard backend parts are ready-made blocks. An admin switches each on once in system.rk and picks its driver; app authors only declare what they need, in one line. By default everything runs on one Postgres and one binary. Reference: system.rk.

yaml
db:        {driver: postgres, url: '${DATABASE_URL}', isolation: shared}
cache:     {driver: memory, max_mb: 64}            # or valkey
queue:     {driver: postgres, workers: 4, retries: 3, dead_letter_after: 24h}
scheduler: {driver: internal, timezone: Asia/Jakarta}
realtime:  {driver: postgres, transports: [sse]}    # LISTEN/NOTIFY; valkey for many nodes
files:     {driver: local, path: ./data/files, max_upload_mb: 20}   # s3 later
search:    {driver: postgres, vectors: false}
notify:
  email:    {driver: smtp, host: '${SMTP_HOST}', from: Kopi Senja <halo@kopisenja.id>}
  push:     {driver: fcm, project: '${FCM_PROJECT}'}
  whatsapp: {enabled: true, connector: whatsapp_business}
auth:
  issuer: https://kopisenja.rangka.cloud
  two_factor: owners
  clients: [{id: omilo, redirect_uris: ['https://omilo.app/auth/callback'], public: true}]
secrets:   {driver: env}
audit:     {enabled: true, retention_days: 365}

Used in one line ​

App file saysKernel doesNeeds
realtime: true on a modelPushes record changes to open screens over SSE (GET /api/v1/events). In v0 every model's changes are pushed, with or without the flagrealtime
schedule: "0 8 * * 1-5" on a flowRuns it on that cron, once across all nodesscheduler, queue
queue: {retries: 3} on an actionReturns 202 and runs it in the background with retriesqueue
cache: 5m on a dashboardReuses computed results per organisation and period, dropped on any writecache
notify: step in a flowSends through the channel's drivernotify

Drivers, transports and connectors ​

  • Drivers serve a capability: Postgres or Valkey for the queue, local disk or S3 for files, SMTP or a log for email.
  • SSE and WebSocket are transports of realtime, not separate capabilities.
  • SMTP, FCM and SMS are drivers under notify, not connectors. Connectors integrate the business with outside services (WhatsApp, QRIS, marketplaces) — see Connectors.

Secrets ​

Secrets are always ${VAR} references, resolved by secrets.driver (environment, a file, or a vault). The validator refuses literal passwords and keys, and /meta redacts every secret value.

v0 status ​

Working: Postgres, memory cache, Postgres queue and scheduler, SSE over LISTEN/NOTIFY, audit, and record attachments on local disk (contract 0011). Logged only: email, push and WhatsApp sending (the log driver writes them to the server log and the audit log). Not yet: Valkey drivers (the cache driver is a stub), S3 (files.driver: s3 is refused at start-up), OpenSearch, vector search, a cache: on models.

Rangka OS is source-available under the Elastic License 2.0 (ELv2). Free to self-host.