Services and Integrations
Set out the client’s accounts, payments, uploads and integrations before the build.
Service setup answers who provides infrastructure. Your request answers what the app should do with it. Say when users need accounts, payments, uploads, AI features, or an outside API, and describe the behavior you expect.
Zeneno-hosted services cover Fly.io, Neon, Cloudflare Pages, R2, and OpenRouter. You can mix them with your own accounts. Stripe always uses your own keys. Other third-party integrations may need credentials, permissions, or configuration that Zeneno cannot create for you.
After the build, ask Zeneno to explain which integrations are live, which need your action, and how to test the important flows.
Authentication
Describe roles, protected pages, sign-up, and account recovery. Tell Zeneno which actions each role may perform.
Payments
Specify products, prices, checkout, subscriptions, and access rules. Connect your own Stripe account when payments are required.
Uploads
Describe who can upload, see, replace, and delete files. Choose Zeneno-hosted R2 or your own storage account.
AI in your app
Describe what the AI feature does and its limits. Its OpenRouter usage is separate from the credits Zeneno spends to build the app.
Make “real” explicit
If a workflow must use a live service, say so and test it in the deployed app. Ask what remains to configure if a provider or credential blocks it.