Deklarative started as the internal platform behind a stack of vertical SaaS products we were building — a compliance copilot, a telephony control plane, a construction OS, a subcontractor payment system, a property-management gate. Each product needed the same scaffolding: entities, forms, reports, workflows, infrastructure. Each one would have taken nine months of plumbing work before we wrote a single line of business logic.

We built the platform once. Now the products take three months instead of nine, and they all share the same code path for the boring parts (auth, audit, RBAC, workflow, codegen, infra). When we fix a bug in the platform, it fixes in all six products. When we ship a new feature in the platform, all six get it for free.

After running it for ourselves long enough to know it works, we're opening it.

What we believe

• Declarative beats imperative. Describe the system, not the steps. The platform's job is to figure out the steps.
• Real code over runtime traps. We generate TypeScript and Go you can read, not bytecode that locks you in.
• Open source by default. Apache 2.0 source. Self-hosted. No usage-based workflow billing.
• Polyglot is right. Different teams write different languages. The platform should not pick for them.
• Boring is a feature. Postgres. Pulumi. BPMN. Temporal-compatible runtime. Standard, durable, well-understood.

The Deklarative product family

We use Deklarative to build everything we sell. The current product family:

• Argitron — compliance copilot (SOC 2, ISO 27001, ISO 42001)
• VoxRidge — vendor-agnostic telephony control plane
• SwiftCrane — construction operating system
• Billitron — subcontractor payment OS
• DwellPort — property management with smart gate access
• GenuStream — messaging fabric

And the platform that runs all of them: Deklarative.