edictIn development

About Edict

Edict is a backend for mobile apps, in development. It exists because AI coding agents made app screens easy to build, and the backend behind them is still the hard part.

Why does Edict exist?

A working app needs more than an interface.

Sign-in, stored data, subscriptions, notifications, AI limits, files, and background work each come from a different place. Each has its own setup and its own ways to fail. Joining them is work, and so is the business logic that keeps them in step.

Take a paid AI feature. The backend has to know who the user is, whether their plan is active, what the plan allows, and how much allowance is left. It has to give the allowance back when a request fails, and react when a plan renews or is refunded. Most apps need rules like these, and each team writes them again.

Edict is designed to make those rules configuration. You choose what the app needs, and the modules are meant to arrive already connected.

What does Edict stand on?

Five principles shape the design.

Design principlesintent, not a spec

  • Complete capabilities, not disconnected APIs

    A module should do a whole backend job. A subscriptions module, for example, should understand verified entitlements and server-side access, not only wrap a payment endpoint.

  • Composition without manual integration

    Modules share typed contracts and events. You say how they should interact, and you do not write the glue between them.

  • Configuration instead of backend programming

    The planned first version has no customer-written backend functions. You configure safe, typed, reusable operations, and Edict handles the implementation.

  • Local development is free and realistic

    You should be able to build and test an app on your own machine, with realistic data and simulated services, before you pay for hosting.

  • Production is a deployment decision

    The configuration you develop with is meant to describe the real backend too. Going live should not mean rebuilding your logic.

Where is Edict today?

Early. The product is designed, and building has started. It is not released.

What exists

  • This website and the beta waitlist.
  • A written product design: modules, configuration, and the local and hosted model.
  • Early engineering on a first technical proof, an example fitness app.

What does not exist yet

  • A beta you can sign up to and use.
  • Released SDKs, CLI, MCP server, or agent skills.
  • Prices, a launch date, or production terms.

How will Edict be licensed?

The plan splits the code between two licenses and keeps some things private. This is the intended direction, not a finished release.

MIT License
Mobile SDKs, the CLI, the MCP server, agent skills, example apps, and public configuration specifications.
Elastic License 2.0
The compiler, the execution engine, core business-logic packages, the local runtime, and core self-hosting components.
Private
Production credentials, customer data, internal commercial operations, and private deployment configurations.

Elastic License 2.0 is source-available. It is not an open source license as the Open Source Initiative defines one. This is the current intended model, and it does not mean every repository is already published under these licenses.

How can I follow along?

Join the waitlist for updates by email, or read along on the blog.

Get an invitation when the beta opens.

Joining gets you email updates while Edict is built, and an invitation to the hosted beta when it opens.

Building now. No launch date yet.