Petal Pro pricing

Developers building a Phoenix app who would rather start from decisions already made than from an empty generator. Multi-tenancy, billing, auth, orgs, admin and background jobs are built once and built the same way, and the optional pieces ship as recipes you add when you need them. The step-by-step guide walks the whole stack if you want to read it before you buy.

A starting point your agent understands. It reads the CLAUDE.md and AGENTS.md files, follows the patterns already in the codebase, and runs the recipes for the changes people make most often. You get features that match the app instead of features that merely work.

The AI files are the smaller half. The value is that the code underneath them is consistent enough to be worth pointing an agent at: four years of multi-tenancy, billing and auth decisions, all made the same way.

One payment buys 365 days of access to the latest Petal Pro and every version released in that window, plus a place on the private GitHub repo and the downloads page. Every purchased tier buys the same 365 days: the tiers differ on projects and seats, not on how long the updates run. Prices are in US dollars and do not include any local taxes you owe. When the year is up you lose repo access and new downloads, you keep every version released while your access ran and the projects you built with them, and you can renew for another year at a lower price.

Yes, and you pay the difference rather than the full price. Buying a tier above the one you already own costs that tier's price minus what you paid for yours, and that holds whether your current year is still running or ran out months ago. The price on the ladder above is the one you will be charged. It buys a full year at the new tier from the day you buy it, and if you had more than a year still to run you keep your own date, at the new tier. If it is a tier you have held before, you pay its renewal price instead, which is lower again.

Yes. Single covers one project, Unlimited and above cover as many as you want, and it makes no difference whether the project is a side hustle, a client build or something you mean to sell later. The one limit is that you cannot build something that competes with our products. The full terms are in the licence, and support@petal.build can answer anything the text leaves open.

No. Publishing the source, directly or indirectly, is the one thing the licence exists to prevent, because the sales are what pay for the work to continue. Build whatever you like with it, as long as the result does not give the code away or compete with our products.

We answer account and licensing questions. We do not review your code, and the assumption is that you already know the Phoenix stack. Technical questions go to our Discord, where we or another member will usually have an answer, though we cannot promise one.

Email support@petal.build within 7 days of your purchase and we refund in full, no questions asked. Renewal terms are in the licence.