Vertical SaaS teams
Building the next industry-specific platform — construction, healthcare, legal, real estate. Deklarative replaces the bottom 60% of your stack so you can ship the top 40%.
Deklarative is one platform with three surfaces: a low-code studio for entities, forms, and reports; a polyglot workflow engine (TypeScript, Kotlin, Go, Rust, Python); and infrastructure automation that provisions Postgres, queues, object storage, and CDNs from the same manifest.
Open source under Apache 2.0. Self-hosted by default; cloud-hosted by request.
$ deklarative apply ./customer-portal/ parsing manifest ok 12 entities · 8 forms · 3 reports generating typescript ok 47 files · tanstack-query hooks generating go server ok 28 files · Fiber + Huma + pgx generating postgres schema ok 32 tables · 14 indexes · 3 RLS policies provisioning infrastructure aws s3 buckets ok 3 buckets rds postgres ok db-cust-portal-prod cloudfront ok d2k...cloudfront.net acm certificate ok *.acme.example.com deploying workflow engine activities 34 registered bpmn processes 8 deployed approval · refund · ... cmmn cases 2 deployed customer-onboarding · investigation $ deklarative open ready https://app.acme.example.com
What "declarative platform" means
Most low-code platforms build the UI and stop. Most workflow engines run processes and stop. Most IaC tools provision cloud resources and stop. Deklarative does all three from one manifest, on one data model.
Define an entity once. Get a CRUD API, a form, a list view, an audit trail, an import/export, a search index, and a report — generated from the entity, not maintained alongside it. XAF-inspired auto-layout, GeneXus-inspired data model.
BPMN processes and CMMN cases on a Temporal-grade engine. Activities written in TypeScript, Kotlin, Go, Rust, or Python — registered once, callable from any process. 56 activities ship: HTTP, GraphQL, email, SMS, Slack, Teams, database, transform, CSV, OCR, e-signature, and more.
Pulumi-driven provisioning of databases, queues, object storage, CDNs, and container runtimes. Same manifest, deployed to AWS, GCP, Azure, Hetzner, or your bare-metal Kubernetes cluster. Reproducible, signed, rollback-able.
Studio, runtime, and workflow engine ship as self-hosted binaries. No vendor lock-in, no usage-based pricing on workflow runs, no surprise tier changes. Your data, your cluster, your audit trail. Apache 2.0 source.
Why Deklarative exists
Modern app teams ship the same scaffolding over and over: an entity model, a form, an audit log, a report, a workflow, a queue, a database. Each new app re-implements it slightly differently and decays slightly faster than the last.
We tried the alternatives. Retool ships a beautiful builder for internal tools but stops at the front end. Temporal is a great workflow engine but doesn't know what your entities are. OutSystems and Mendix offer end-to-end low code but lock you in to a runtime you can't reason about. Camunda has the workflow story without the data story. Pulumi has the infrastructure story without the application.
The product we wanted was the union — declarative entities, forms, and reports (XAF-style); a real workflow engine (BPMN + CMMN, Temporal-grade); polyglot activities (so the AI team can write Python while the platform team writes Go); and infrastructure provisioning that's part of the deploy, not a separate ops ritual.
We built it. We shipped Argitron, VoxRidge, SwiftCrane, Billitron, and DwellPort on it. Now we're opening the platform.
| Stitched stack | Deklarative |
|---|---|
| Retool + Temporal + Pulumi + Postgres + ad-hoc CRUD code | One manifest, one platform, one deployment |
| Per-tool licensing — easy to hit $100k/year on small teams | Apache 2.0 self-hosted; cloud only if you want it |
| Workflow engine doesn't know your entities; entities don't drive workflow | Same data model drives entities, workflow, and codegen |
| Three teams (frontend, workflow, infra) shipping at three different cadences | One manifest applied — frontend, workflow, infra deploy together |
| Activities locked to one language | Activities polyglot — TS / Kotlin / Go / Rust / Python |
What's in the platform
Built with Deklarative
We don't ship a platform we don't use. Every product below is built on Deklarative — same Studio, same workflow engine, same codegen. The platform's quality bar is whatever lets us ship these products without breaking ourselves.
The compliance copilot. SOC 2, ISO 27001, ISO 42001 as an automated outcome.
argitron.com →Vendor-agnostic telephony control plane. Asterisk, FreeSWITCH, Cisco, 3CX, Twilio behind one API.
voxridge.com →The contractor's operating system. Project management, financials, quality, safety on one model.
swiftcrane.com →Subcontractor payment OS. Quotes, AIA pay-apps, lien rights, ACH collection.
billitron.com →Property management with the gate built in. ANPR, tenant portal, leases, ledger.
dwellport.com →Messaging fabric. Notifications across email, SMS, push, chat, in-app — 58 providers, 4-level preferences.
genustream.com →At a glance
Who Deklarative is built for
Building the next industry-specific platform — construction, healthcare, legal, real estate. Deklarative replaces the bottom 60% of your stack so you can ship the top 40%.
Consolidating dozens of internal apps onto one shared model. Same Studio for HR onboarding, AP automation, vendor management, and audit workflows. One platform team, many apps.
Three people, 90 days, one shippable product. The boilerplate kills you when you're small. Deklarative ships you the boilerplate.
"We use Deklarative to build the products we sell. The compliance platform, the telephony control plane, the construction OS, the subcontractor payment system, the property-management gate — all run on the same Studio, the same workflow engine, the same codegen. The platform is the product."
— Deklarative team · See what's built →
Open by design
Apache 2.0 source. Self-hosted by default. No usage-based workflow pricing. No proprietary lock-in. The code Deklarative generates is yours; the platform is yours; the data is yours.
Standards & integrations
Plus CEL for expressions, NATS / Kafka / Redis for queues, and Cosign-signed releases. See the platform →
Get started
Open source under Apache 2.0. Cloud free for evaluation. Production deployments self-hosted or hosted, your call.