Help centre

A plan gives you build prompts, a database schema with security rules, a phased execution list, a monthly cost model, a launch checklist and a marketing plan. It does not write your application, host it, or take payments for you. It is the planning layer that sits before all of that.

Say who it is for, what they do in it, and how money moves. Two or three sentences beats a bullet list. Naming a constraint — one screen, no accounts, must work offline — shapes the plan far more than naming a technology.

To do, in progress and done. The middle state exists because half-finished work is the thing that actually needs tracking. Click a task's circle to advance it; click again from done to reopen it.

Everything is editable, and you should edit it. Costs, checklist items and the plan stage all write immediately. The generated plan is a strong first draft that saves you a day, not something to obey.

Publishable keys are designed to be visible — Stripe's publishable key is safe in a bundle. Secret keys, API tokens and webhook secrets never are. If a key can spend money or read another user's data, it belongs in a backend environment variable and nowhere else.

Filtering a list in the UI is not security — anyone can call your API directly. Row-level security enforces ownership at the database, so a request for another user's rows returns nothing regardless of what the client asks for. Test it by logging in as a second user and confirming an empty list.

You keep full access until the end of the period you have already paid for. After that, plans stay readable and exportable. Nothing is deleted when a subscription lapses.

If Kivo47 did not do what it said it would, write to support within 14 days of the charge and it is refunded. The refund policy page has the exact wording.