edictIn development

AI photo and content tools

An example app where users upload photos, run AI processing in the background, and spend credits or plan allowances.

Example app Built from planned modules. Not a customer. Not a supported app today.

Illustrative rule: reserve a credit, release it on failure

AgentEdit edict.yaml+11illustrative
1modules:
2+ credits:
3+ balance: image_credits
4+ reserve:
5+ per_request: 1
6+ release_on: failure
7+ jobs:
8+ render_image:
9+ on: image.requested
10+ retries: 3
11+ ai_avatar:
12+ requires_plan_or_credits: true

Placeholder values and unfinished syntax. Not a released feature.

What is the AI photo and content tools example app?

A user picks a photo, chooses a style, and taps a button. The result arrives after a short wait, often as a notification. Free users have a few tries. Others buy credits or subscribe for more.

This category is a design target. It is not a claim that Edict already supports a complete photo or content app.

What backend does the AI photo and content tools example need?

  • Uploads.
  • Storage.
  • AI provider integrations.
  • Background jobs.
  • Credits and quotas.
  • Subscription access.

How do the planned modules compose in the AI photo and content tools example?

This category uses many modules at once, which is why it is a useful test of composition. Files is designed to accept the upload and store it under the user’s ownership. The AI gateway is designed to call the provider with credentials kept on the backend. Generation can take time, so Background jobs are planned to run it with retries and to survive a client disconnect. The result would be saved back to Files.

Payments and credits are designed to reserve a credit before the work starts, spend it on success, and release it if the work fails. Subscriptions could grant an allowance instead. Authentication would tie all of it to one person.

Authentication, Files, AI gateway, and Background jobs together are designed to cover the path from upload to finished image.

What would an illustrative rule look like in the AI photo and content tools example?

The configuration above reserves one credit per request and releases it on failure, retries the job, and lets access come from a plan or from credits. The key names and the syntax are placeholders and are not final.

What is example and what is planned in the AI photo and content tools example?

All modules named here are planned and in development. Your app owns the models, the prompts, the style options, content moderation, and compliance with provider terms and platform payment rules. Edict is designed to handle storage, access, metering, and retries. It does not judge the images.

See the AI gateway and Payments and credits module pages for the planned design. Join the beta waitlist to follow progress.

These share the most modules with this one.

See all example apps

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.