DAPITA CORE
LAUNCH PRICING · LIMITED MONTHLY SLOTS

A sandboxed plugin engine for people who build things.

DAPITA Core is a self-hosted application engine where every plugin runs as an isolated process — signed IPC over Unix sockets, AppArmor profiles, no direct database access. Write plugins in Go, hot-reload without restart, generate them with AI, deploy on your own VPS.

Built by developers who got tired of monolithic CMSs, fragile WordPress plugin trees, and YAML-glued Docker zoos.

See Launch Prices →
~/my-plugin/plugin.json

How It Actually Works

Engine speaks DPP (DAPITA Plugin Protocol) over Unix sockets with HMAC-SHA256 signatures. Plugins never touch the database directly — every query goes through the engine's DB proxy.

DAPITA Engine Go · DPP router · auth Plugin: catalog sandboxed process Plugin: orders sandboxed process Plugin: messenger sandboxed process Plugin: your-own AI-generated PostgreSQL · sharded accessed only via DB proxy DPP / HMAC DB proxy

What's Actually In The Box

Not a SaaS. Not a CMS. A real engine with 14 plugins included that you can study, fork, and extend.

🛡️ Process Isolation

Every plugin runs as a separate OS process with its own user, AppArmor profile, and limited filesystem access. DPP signatures verify every message between engine and plugins.

🗄️ DB Proxy

Plugins cannot connect to PostgreSQL directly. All queries go through the engine's DB proxy with row-level access control and per-plugin schemas.

🔥 Hot Reload

Replace a plugin binary without touching the engine or other plugins. Lazy idle plugins exit cleanly on inactivity and respawn on first request.

🤖 AI Architect

Describe a plugin in plain English, get a working DPP-compliant implementation. Generated code is yours — no API dependency at runtime.

🗂️ Sharded Database

21 schemas, products partitioned A–Z, events partitioned by month. Linear horizontal scaling without cross-shard queries.

🔒 Vault-Backed Encryption

AES-256-GCM field-level encryption with HashiCorp Vault, automatic 90-day key rotation, Shamir secret sharing for disaster recovery.

14 Core Plugins Included

Each one is a working reference implementation of DPP — read the source, copy patterns, build your own.

Loading plugins...

vs The Alternatives

What the other paths actually cost in time, complexity, or freedom.

Build It Yourself

  • Plugin protocol designweeks
  • Sandbox + IPC securityweeks
  • Hot reload plumbingweeks
  • Sharded DB layermonths
  • AI plugin generationmonths
  • Total time to ship~1 year

DAPITA Core

  • DPP protocolincluded
  • AppArmor sandboxincluded
  • Hot reload + lazy idleincluded
  • Geo-sharded PostgreSQLincluded
  • AI Architect plugin genincluded
  • Time to first pluginsame day

Launch Pricing

Each tier has a fixed slot count per month. When slots fill, the next tier opens at a higher price. Counters reset on the 1st of every month.

Loading prices...

⏳ Important: Launch Activation Delay

Discount tier licenses purchased at launch pricing activate 90 days (3 months) after purchase. Your slot and price are locked in immediately, the engine, plugins, and marketplace access become available 3 months from the purchase date.

The delay applies equally to every discount tier buyer. Entity licenses (lifetime) and full-price licenses activate immediately — only discount tier purchases have this delay.

Common Questions

What language are plugins written in?
Any language that can speak DPP over a Unix socket and produce HMAC-SHA256 signatures. The reference implementations are in Go, but the protocol is language-agnostic. Rust, Python, and Node.js plugins work the same way.
How is this different from WordPress + plugins?
WordPress plugins run inside the same PHP process as the core. One bad plugin can crash the whole site, leak memory, or read any database table. DAPITA plugins run as isolated OS processes with their own users and AppArmor profiles. The engine cannot be crashed by a plugin, and a plugin cannot read data outside its assigned schemas.
Can I write a plugin that needs my own external API?
Yes. Plugins can make outbound HTTP calls through the engine's HTTP proxy with allowlisted domains declared in plugin.json. The engine logs every request and enforces rate limits per plugin.
What does deployment look like?
Single static Go binary for the engine, plugins are tar.gz archives with manifest. Install on any Linux VPS with PostgreSQL and Redis. The setup wizard provisions DNS, SSL via Let's Encrypt, and database migrations automatically.
What if I don't renew next year?
Engine and plugins keep running on your server. Updates pause and the marketplace stops serving new plugin downloads to your installation, but nothing is deleted and nothing stops working. Renew anytime.
Where does the source code live?
The engine and core plugins are not currently public open-source — they are licensed binaries with full source disclosed to license holders for audit and modification. You can read, fork internally, and modify any plugin you have a license for.

Ready to Stop Fighting Your Stack?

Lock in launch pricing before this month's slots are gone. Slots reset on the 1st.

Claim Your Slot →