edictIn development

How Edict works

You describe the app to your coding agent. It edits one file, edict.yaml. You run and test the backend on your own machine, then move the same file to managed hosting when you are ready.

Planned This is the intended workflow. Edict is in development and none of it is available yet.

  1. Describe

    Tell your coding agent what the app needs, in plain words. Through the planned CLI and MCP server, the agent can read what Edict offers, so it picks modules instead of inventing a backend.

    You, to your coding agent. Illustrative.
    Build a fitness app with Apple login, workout tracking, premium AI coaching, and daily reminders.

  2. Configure

    The agent edits edict.yaml to choose modules and set their rules. You review a diff, as you would review any code.

    Connections between modules, such as a plan that limits an AI feature, are designed to be resolved for you.

    Modules: Authentication and user management, Subscriptions and paywalls, AI gateway

    edict.yamlillustrative
    modules:
  identity:
    providers: [apple, google]
  subscriptions:
    plans: [free, premium]
  ai_coach:
    requires_plan: premium
    quota:
      per: billing_period
      limit: 200

  3. Develop locally

    Edict is designed to start a backend on your machine, with local PostgreSQL, seeded users, simulated purchases, mock notifications, and simulated AI responses.

    You need no hosting account and no live provider keys. Local development is planned to be free.

    Modules: Database and backend APIs, Background operations

    Terminal, illustrative
    $ edict devPostgres ready on localhost:5432Backend ready on http://localhost:8787

  4. Test

    Scenario tests are designed to run the hard cases: an expired subscription, a spent allowance, a failed AI call, a schema change.

    Simulated services do not prove that a real provider works. Provider test environments still matter before launch.

    Modules: Declarative business logic, Subscriptions and paywalls, Payments and credits

    Terminal, illustrative
    $ edict testfree user       402 upgrade required   passpremium user    200 remaining          passAI call failed  allowance released     pass3 passed, 0 failed

  5. Deploy

    When you are ready, the same edict.yaml is designed to move to managed hosting. You check it against real provider test environments, add production credentials, and ship.

    The planned path is a hosted trial first, then a paid production plan.

    Modules: Push notifications, Payments and credits, Files and content delivery

    Planned stagesnot final
    Local development
    Free. No subscription.
    Hosted trial
    A limited trial. Length and limits are not final.
    Paid production
    Managed hosting on a paid plan. Pricing to be decided.

  6. Scale

    Edict is planned to run your backend on managed hosting, so you do not run servers as your app grows.

    Capacity, limits, regions, and performance are not set yet. This page makes no promise about them.

    Modules: Background operations, Database and backend APIs

    Still openno promises yet
    Hosting regions
    Not decided
    Usage limits
    Not decided
    Performance targets
    Not decided
    Security guarantees
    Not decided

Local or hosted?

Local development uses simulated services on your machine. Hosted production is planned to use real ones. The same edict.yaml describes both.

Local developmentHosted production
IdentitiesTest usersReal users
Subscriptions and paymentsSimulated purchases and payment eventsReal entitlements from the app stores
DataSeeded PostgreSQL on your machineManaged storage and APIs
NotificationsMock notificationsProvider integrations
AI requestsSimulated responsesRequests to your AI provider through the gateway
ConfigurationYour edict.yamlThe same edict.yaml
CostPlanned to be freeA trial, then a paid plan. Pricing to be decided.

Simulated services do not prove a real provider integration works. Production still needs validation against real provider test environments. See pricing for what is decided.

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.