Go · Edge · Headless
Go-native. Edge-native. Headless.
GOKIRI ERP is a compiled Go service on Cloudflare Workers — not a VM monolith with an API bolted on. Lightweight by architecture, not by missing features.
Architecture
Web
POS
Mobile
Integrations
edge-api-gateway
JWT · tenant routing
gokiri-core
Go Worker · headless ERP API
Tenant D1
ledger
Tenant R2
documents
App Market
Service Binding
Why Go on Workers
Compiled, small binary
Fits Workers CPU and memory limits. No JVM heap or PHP-FPM process pool.
Strong typing for finance
Explicit error handling and static types for ledger logic you can trust in production.
No interpreter overhead
Contrast with PHP/Python ERP stacks — predictable latency on every request.
One codebase, many triggers
API handlers, Cron Triggers, and queue consumers share the same Go Worker binary.
Headless edge server
- ✓UI is optional; the REST/JSON API is canonical.
- ✓portal.gokiri.com is one client among many — build your own.
- ✓Service Bindings enable zero-hop app-to-core on the same Cloudflare account.
- ✓JWT gateway verifies tokens and injects tenant context before reaching gokiri-core.
BYOC deployment
Bring Your Own Cloud — your data never leaves your Cloudflare account.
- ✓Tenants provision Workers, D1, and R2 in their own Cloudflare account.
- ✓The control plane orchestrates deploy — it never stores your CLOUDFLARE_API_TOKEN.
- ✓Optional CloudBackup tier replicates to a secondary region for DR.
- ✓Setup guide: docs.gokiri.com/deployment/byoc-setup
VM ERP vs GOKIRI edge
Before (VM ERP)
With GOKIRI
Provision VM, DB, Redis
wrangler deploy to your account
Patch OS + runtime
Cloudflare manages edge runtime
Scale vertically
Scale globally by default
Monolith UI + API
Headless API + thin clients