Skip to content
Taslim Tareq
Book a 15-minute call

All software

BusinessOS

A multi-tenant platform in Go for configurable ERP, POS and CRM, with one core and no per-industry forks

Type
SaaS platform
Status
Private system
Year
2026
BusinessOS module map with 27 modules in five layers, from platform core through access, configuration engines and business modules to edge and distribution, with self-monitoring across all of them
Module map drawn from the repository's module docs in October 2026. BusinessOS has no user interface yet.

BusinessOS is a business operating system I’m building in Go. Each business switches on the modules it needs and configures its own ERP, POS and CRM without new code.

Entities, fields, forms, workflows, automations and roles are data that each tenant defines, and engines interpret that data at runtime. Twenty-seven modules are built so far: platform core, authentication, tenant and organization management, user management, a field-level permission engine, the dynamic entity engine, the form builder, the workflow, automation and notification engines, inventory and sales, purchase, POS, accounting, CRM, HR, reports, dashboards, a public API, an AI assistant, integrations, a marketplace, white-labelling, a mobile sync API and self-monitoring.

I record design decisions as ADRs, 39 so far. One example: I built the entity engine before the permission engine, because field-level permissions need fields to exist first.

How it works

  1. Platform core
  2. Authentication and tenants
  3. Dynamic entity engine
  4. Permission engine
  5. Form builder
  6. Workflow engine
  7. Automation and notifications
  8. Inventory and sales
  9. Purchase, POS and accounting
  10. CRM, HR and reports
  11. Public API and integrations
  12. AI assistant
  13. Self-monitoring

Engineering decisions

  • Fields, forms, workflows, automations, reports, dashboards and roles are metadata that each tenant configures. The aim is one platform that serves restaurants, pharmacies, clinics, retail and manufacturing without code changes.
  • The dynamic entity engine publishes a JSON Schema for every entity a tenant defines, with relationships, computed fields, and record import and export.
  • A form only arranges fields. Leaving a field off a form hides nothing and adding one grants nothing, because permissions live in their own engine.
  • The workflow engine moves records through states and transitions, with conditions evaluated on the server and approval steps.

Built with

  • Go
  • PostgreSQL
  • Multi-tenancy
  • JSON Schema
  • REST API

Want something like BusinessOS?

Book a 15-minute call