Emergent

You will like the reach: web and mobile from one conversation, forking a project to try a second direction without losing the first, and a custom domain when it is done. That is the daily trait, one chat that ends in two app stores and a URL.

You will not like debugging something an agent built, tested and shipped on your behalf, because the moment it breaks you are reading generated code in a browser tab. Pick it for the mobile prototype you need to show someone next week. Pick Lovable if the browser is the only target you care about.

The gap is the claim. The help center calls Emergent the world's first truly agentic vibe coding platform, and nothing on the page defines truly, agentic, or first, which is marketing, not documentation. The documented safeguard against a bad deploy is a Rollback Feature, which means bad deploys are an expected part of the workflow.

The consequence: treat every deploy as a candidate, keep the previous version one click away, and do not point a custom domain at anything until a human has used it. What it does right: Context Limits are documented as a constraint rather than hidden, so you learn the ceiling before you hit it.

Emergent publishes no benchmark. The documented pipeline: 1. Agents design, build and test the application. 2. A Pre-Deployment Health Check runs before release. 3. Custom agents can spawn sub-agents for delegated work. What is not documented is what test means, which tests, written by whom, and what the health check inspects, so the verification step is a label rather than a method.

The consequence is that the gate cannot be audited from outside, so it earns no more trust than the model behind it. A published list of the health check's checks would move the reliability score. The observation: a gate is only as strict as its published criteria.

A Y Combinator S24 company that raised $70M from SoftBank and Khosla in 2026, which is real runway in a category where the model vendors set the cost of goods. The pricing tells the strategy: a Pro tier at $200 a month aimed at heavy users who subsidize everyone else, the standard shape when gross margin on the free tier is negative.

Moat: none yet beyond speed, and speed is not a moat. Likely acquirer is a cloud that wants a builder with a mobile story. Position: funded through 18 months, watch the gross margin line before the growth line.

The demo builds an app from a chat. Procurement: Standard at $20 per month is $1,200 for sixty, each seat with 100 credits and private hosting, and Business and Enterprise are custom, so the number that matters sits behind a sales call. No SSO, SCIM, audit log or retention terms appear on the pricing page, and a hosted builder that deploys on our behalf needs all four.

Nothing runs in CI, so the platform sits beside the pipeline rather than inside it, which limits it to product prototyping teams. Onboarding is a login. What would change the verdict: a published Business price with SSO and a retention statement. Not yet.

Closed platform. I cannot bring a key for the builder and I cannot run it against my own box. Two things are scriptable: a universal key that drops LLM access into the generated app with one click, and MCP in two directions, integrated connectors and external servers I stand up myself.

GitHub export gets the code out, which is the escape hatch that matters, because a generated app I can read is a generated app I can leave with. Nothing else is mine: no prompts, no model choice, no config file. Fine for a prototype, not for anything I intend to keep.