Anything

The trait you feel daily is the credit balance. Everything you do draws it down, so the experience of using this is the experience of watching a number fall while you iterate, and iterating is the entire point of a prompt-to-app tool. That tension shapes how you work more than any feature does.

Use it for a demo, a form, an internal dashboard, the sort of thing that exists for six weeks. Pick Lovable or v0 when the output has to become a real codebase, because those communities are larger and the exit path is better travelled.

The meter has no stated unit of work. Tiers are quoted as monthly credit allowances, and there is no documented mapping from a credit to a page, a component or a revision, which means a buyer cannot estimate consumption before committing to a plan. An agent that loops on a hard request spends the budget faster and tells you afterwards.

Measure your own burn on the free plan for a week before upgrading. What it does right: a free plan exists, so that measurement costs nothing but time.

There is very little here to assess. The record names a frontier model and more than forty third-party integrations, and states nothing about how requirements become code, how generated code is checked, or whether anything executes before a user sees it. A model name is a procurement fact, not a design.

The documentation is thin in the literal sense, and this row is unverified, so every capability listed should be read as a claim from marketing material rather than an observation. No benchmark exists, which is consistent with a category that has no accepted measure of success.

The rename is the most informative event on file. Companies do not abandon an established product name and its search results casually; they do it when the category label has become a liability or the original positioning stopped converting. Widening to a name that claims everything is a bet on optionality rather than on a defended niche.

Moat: none visible, since the model, the hosting and the integrations are all bought in. Likely path: acquisition by a platform wanting the front end, or a further pivot. Position: pass, and revisit if retention numbers ever become public.

The individual plan at $19 multiplies to $1,140 a month at our headcount, and it is the wrong shape: sixty separate allowances that cannot be pooled, so some engineers exhaust theirs while others waste theirs. The tier designed for organisations has no published price, which means a call before I can even build a business case.

There is no identity federation, no audit of what was generated, nothing that runs in our pipelines, and the output lives on their infrastructure. Not yet. If a team needs it, one shared account on a card with a limit.

There is nothing here I can own. The model is chosen for me and cannot be swapped, there is no endpoint to redirect, no local option, and no MCP in either direction. Everything runs on their servers and stops when they stop.

What bothers me most is the export question, which the record does not answer. If the code I generated cannot leave, then what I bought was a tenancy, not a program, and the thing I built is collateral for a subscription. Somebody will tell me this is fine for prototypes. It is, and I still want the tarball.