edictIn development

Subscriptions and paywalls

Planned store subscription sync, entitlements, and backend enforcement of paid access.

PlannedMonetization module. Not available yet. Edict is in development.

Illustrative plans and entitlements

AgentEdit edict.yaml+8illustrative
1modules:
2+ subscriptions:
3+ plans: [free, premium]
4+ entitlements:
5+ premium: [ai_coach, export]
6+ trial:
7+ enabled: true
8+ ai_coach:
9+ requires_plan: premium

The syntax is not final. Your coding agent would edit this file.

What is the planned Subscriptions and paywalls module designed to do?

Subscriptions are a major focus for Edict. The planned module covers Apple App Store subscriptions, Google Play subscriptions, RevenueCat integration, subscription lifecycle synchronization, entitlement management, premium feature authorization, trials and expirations, cancellation and refund handling, paywall integration, and subscription-aware usage quotas.

The goal is not just to display a paywall. It is to make sure paid access is enforced correctly by the backend. A paywall that only hides a button can be bypassed. A backend that checks the entitlement on each request cannot be skipped in the same way.

How does the Subscriptions and paywalls module connect to other modules?

The subscriptions module is designed to provide an entitlement contract. Other modules can require it.

  • Subscriptions + Authentication. Purchases are designed to belong to a user, and the entitlement to be looked up for the person making the request.
  • Subscriptions + Authentication + AI gateway. This is the pattern of subscription-gated AI. The gateway is designed to check identity, check the entitlement, and then apply a usage quota that can reset each billing period.
  • Subscriptions + Push notifications. Lifecycle events, such as a trial ending soon, can trigger a notification you approve.
  • Subscriptions + Business logic. Rules such as “free users get three exports a week” are designed to be expressed as configuration over the entitlement.
  • Subscriptions + Payments and credits. Some apps combine a plan with extra credit packs. The two modules are designed to keep their balances separate and consistent.

What would you configure in the Subscriptions and paywalls module?

You name your plans, map each plan to the entitlements it grants, and set trial behavior. Then you attach entitlements to the features that need them, for example requires_plan: premium on an AI feature. You also set quota rules for paid plans.

The configuration on this page is illustrative. The syntax is not final.

What stays your own code with the Subscriptions and paywalls module?

The paywall design and the purchase flow in the app stay yours. So do pricing and plan decisions, and the store listings and review process. Edict does not publish prices on this site, and plan prices are your own decision. The module is designed to respect App Store and Google Play payment policies, and you remain responsible for meeting them.

Is the Subscriptions and paywalls module available yet?

Planned. Edict is in development, and this module is not available. Store and RevenueCat integrations, trial terms, and refund behavior are not claimed until each is built, tested, and released. Nothing here is a promise of dates.

Join the beta waitlist to hear when the status changes.

What does the Subscriptions and paywalls module work with?

Subscriptions and paywalls is designed to connect to 6 other modules. The lit arcs on the map show which.

Composition mapplanned, illustrative
  • Authentication and user management

    Planned sign-in, sessions, profiles, and ownership rules that every other module can build on.

  • Payments and credits

    Planned store purchases for credits, with credit balances and atomic, refund-aware accounting.

  • Push notifications

    Planned device registration, templates, and event-triggered or scheduled notifications.

  • AI gateway

    Planned secure AI provider access with metering, quotas, rate limits, and streaming.

  • Files and content delivery

    Planned uploads, object storage, secure URLs, and file authorization tied to your users.

  • Declarative business logic

    Planned typed rules for quotas, streaks, capacity, credits, and state changes, written as configuration.

Common questions about the Subscriptions and paywalls module

Short answers about this planned module.

Does this show a paywall screen?
The goal is broader than a screen. The module is designed to make sure the backend enforces what a plan allows. Paywall presentation stays in your app.
Which stores and billing tools are planned?
Apple App Store subscriptions, Google Play subscriptions, and RevenueCat integration are planned. None of these integrations is available yet.
What happens when a subscription is cancelled or refunded?
Cancellation and refund handling is a planned part of the lifecycle sync. Exact behavior is not final.

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.