Declare the vertical
An industry is a YAML file — its entity names, phase graphs, budget categories and workflows. That config is the whole definition of a vertical.
Multi-tenant SaaS · Production Management
One plan.
Every vertical.
Thittam · திட்டம்
Thittam is one production-management platform that speaks your industry’s language. Film, construction, software, live events — each tenant gets its own entities, phases, budgets and workflows from a single declarative config. One codebase. Many verticals.
In active development · two demo verticals seeded — film (INR) & construction (USD)
- 🎬 Film production
- 🏗 Construction
- 💻 Software delivery
- 🎪 Live events
How it works
A vertical is a config file, not a codebase
The engineering differentiator: the industry lives in configuration, read at request time.
Services adapt at request time
The same API endpoint behaves differently for a film tenant than a construction firm, because the vertical config tells it how. A new industry is a config change, not a code change.
One system, many tenants
Each tenant’s data lives in its own PostgreSQL schema. A pooled connection routes every request to the right schema — no cross-tenant leakage, by design.
Under the hood
Built like infrastructure
Nine services, one event backbone, strict tenant isolation.
Vertical plugin system
Add an industry with a configuration file, not a fork. One codebase adapts its language, phases, and budgets to each tenant.
Nine Go microservices
Project, budget, expense, ledger, inventory, reporting, IAM, notifications, document — synchronous over gRPC, asynchronous over NATS JetStream.
Tenant-per-schema isolation
Every tenant gets a dedicated tenant_<uuid> schema. SET search_path on the pooled connection keeps data separate with no application-layer joins across tenants.
Real double-entry accounting
A general ledger, purchase orders, receipts, petty cash, and budget versions with approvals — production finance, not a spreadsheet.
Gateway + event backbone
Kong fronts REST/JSON for consumers; gRPC connects services directly; NATS JetStream carries the events between them.
Docs as a first-class artifact
Eleven standard architecture diagrams and the ADRs live alongside the code in a companion docs repo — the design is versioned with the system.
Production management, in any industry.
Thittam is in active build. The architecture, ADRs, and API specs are open to read — the platform speaks film and construction today, with more verticals arriving as configuration.