Skip to main content
DEKLARATIVE
Menu
The declarative low-code platform

Describe the system. Ship the system.

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.

Built with Deklarative Argitron · VoxRidge · SwiftCrane · Billitron · DwellPort
$ 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
One manifest. Generated code. Provisioned infra. Deployed workflow.

What "declarative platform" means

Declare the entities, forms, workflows. Skip the boilerplate.

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.

Entities → forms → reports

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.

Workflow that speaks five languages

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.

Infrastructure as a side effect

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.

Self-hosted by default

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

The boilerplate problem nobody quite solved.

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 codeOne manifest, one platform, one deployment
Per-tool licensing — easy to hit $100k/year on small teamsApache 2.0 self-hosted; cloud only if you want it
Workflow engine doesn't know your entities; entities don't drive workflowSame data model drives entities, workflow, and codegen
Three teams (frontend, workflow, infra) shipping at three different cadencesOne manifest applied — frontend, workflow, infra deploy together
Activities locked to one languageActivities polyglot — TS / Kotlin / Go / Rust / Python

At a glance

The numbers behind the platform.

5 langs
Workflow activities in TypeScript, Kotlin, Go, Rust, and Python — registered once, callable from any process.
56
activities ship in the standard library — HTTP, GraphQL, email, SMS, Slack, OCR, e-sign, LDAP, WhatsApp, more.
6 SaaS
vertical products built on Deklarative — Argitron, VoxRidge, SwiftCrane, Billitron, DwellPort, GenuStream.
Apache 2.0
open source. Self-hosted by default. No usage-based workflow billing. No vendor lock-in.

Who Deklarative is built for

Engineering teams that want to ship the system, not the boilerplate.

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%.

Enterprise platform teams

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.

Founder-led startups

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

The protocols and runtimes your team already knows.

BPMN 2.0
Workflow
CMMN 1.1
Cases
OpenAPI
Generated
Pulumi
IaC
PostgreSQL
17+
Temporal
Compatible

Plus CEL for expressions, NATS / Kafka / Redis for queues, and Cosign-signed releases. See the platform →

Get started

Describe the system. Ship the system.

Open source under Apache 2.0. Cloud free for evaluation. Production deployments self-hosted or hosted, your call.