Pomela
Seed · September 2026

Software that cannot break.

Describe a business. Get a working app in seconds, with its own management area. Then keep it verified, with signed proof, for as long as it runs.

50–76%

Drop in traffic to vibe-coding tools in spring 2026. Owners tried AI-built apps and left.

21.1%

Annual retention of AI apps versus 30.7% for the rest. The apps did not keep working.

91.5%

Of vibe-coded apps ship at least one flaw invented by the model. Nobody signs off on what was built.

Why now · the builders fled upmarket and left the people who need software most01 / 08
Problem

The AI app boom produced apps nobody can trust, then abandoned the people who needed them most.

They break

  • A leading builder shipped a broken-access flaw that stayed open for 48 days across customer apps.
  • In April 2026 an AI agent deleted a startup's production database and its backups.
  • 88.4% of organisations report at least one incident caused by an AI agent.

Owners were left behind

  • v0 now sells more than half its revenue to enterprises; Bolt moved onto Azure. The small-business lane emptied out.
  • A salon, a clinic or a tutor still needs a booking app with an owner area, on their phone, today.
  • Their only alternatives are template sites or a 20% commission marketplace.

Cleaning up costs more than building

  • Human clean-up of an AI-built app runs $500 to $8,000 per app.
  • 88% of enterprise AI pilots fail, and the top reason is an evaluation gap: nobody can say what actually works.
  • Insurers now underwrite AI risk on evidence. There is no standard evidence for a finished app.
Sources · RevenueCat State of Subscription Apps 2026 · public disclosures on Lovable, PocketOS, v0, Bolt · Pomela market research, Sept 202602 / 08
Product · recorded in production, unedited actions

One prompt to a working app. One signed proof that it still works.

Create
A working booking app in 6 seconds, assembled from a production-proven recipe. Customers book; the owner confirms from a private management area.
Edit
Plain-language edits land in a draft. Editing draft · live app unchanged Publish is one atomic step.
Assure
Run the published app like a real user, every control, and issue a Proof Passport: what worked, what failed, what was never tested. Signed, scoped, expiring.
Control
Verified Change plus an agent steward: a change ships with proof the journeys still pass.

Hebrew is native, right to left, on the same engine. Deep multi-screen generation is the next build mode.

Demo app · booking for a boutique day spa · customer, owner and editor surfaces · pomela.app03 / 08
Traction · pre-launch by design

The engine is measured before it is marketed. Every number below was produced in production.

5,320

Apps built through the production pipeline, 933 of them in the last 30 days. Closed access, 0 external users, by choice.

count · D1 app_metadata · 2026-09-07

$0.033

Measured cost of goods per build across 2,589 builds. At $19 per month that is a ~91% gross margin; the exit template below is being rebuilt by its acquirer to reach 60%.

3,250 / 3,250

Tampering attempts rejected by the Proof Passport signature scheme. Deterministic judge accuracy 0.954 against 0.800 for a frontier model and 0.477 for a cheap one.

What is proven today

  • 6 of 37 app categories production-proven end to end, including booking and money flows; 5 more built and awaiting final sign-off.
  • Real money: live PayPal subscription charge succeeded; exactly-once payments proven under 300 concurrent attempts, no double charge.
  • 6,628 automated tests on the current release; disaster-recovery restore drilled on the production database.

Business model

  • Create · owners pay $19 to $69 per month for an app that runs their business.
  • Verify · $149 to $499 per app to run it like a user and issue a signed passport, then a recurring continuous passport.
  • Platform · builder platforms license verification for every app they generate, business to business to consumer.
All figures from Pomela's evidence bundle · counts are QA and founder builds, not customer usage04 / 08
Market · built bottom-up, assumptions shown

Two funnels, one engine: owners who need an app, and everyone stuck cleaning up AI-built ones.

Create · Israel beachhead

10,000 paying owners

× $29 average per month = $3.5M ARR. Israel first: founder-led distribution in Hebrew, WhatsApp and Facebook business groups, and a documented wedge of owners angry at 20% marketplace commissions.

Verify · the door we open first

50 agencies and dev shops

× 20 inherited apps a month × $199 = $2.4M ARR, replacing $500 to $8,000 of human clean-up each. Buyers: agencies, fractional CTOs, and teams inheriting Lovable, Bolt and v0 apps.

Platform · where it compounds

2 builder platforms

× $25K per month = $0.6M ARR, and every one of their generated apps becomes a passport holder. Platforms are being pushed to prove safety; none can do it independently.

The recurring engine, not one-off audits, is what earns the multiple. $8–12M ARR at 8–12× revenue, or ~$5M ARR at ~20× to a strategic buyer, is the range the recent comparables paid. Base44 sold to Wix for $80M cash at $3.5M ARR, with earn-outs of roughly $128M more; under Wix it reached $150M ARR in 11 months.

Illustrative bottom-up · every input is an assumption to be replaced by measured data in the first 90 days05 / 08
Competition

Every competitor sells one link of the chain. No leading vendor sells the whole proof.

CapabilityLovable · Bolt · Base44QA Wolf · Momentic · MeticulousCodeRabbit · QodoLovable TrustCenter · Replit Security AgentPomela
Working app for a non-technical owner, with a management areapartial
Runs the finished app like a real user, every controltests you writestatic scan
Checks permissions and persistence across owner, customer and staffpartial
Maps claims to evidence, lists what was never testedPR-shaped
Signed, scoped, expiring attestation (open format)
Draft → verified → atomic publish; safe autofixdraft onlyPR fixes
Independent of the platform that built the appself-scanmethodology + open format

Why builders cannot copy it

Generating more code faster is their business; proving it is a conflict of interest. Their margins cannot carry a verification fleet either: the category leader's acquirer is building its own model to reach 60% margin. Pomela builds at $0.033.

Where collision comes from in 6–12 months

Exploratory QA agents and "govern AI code" review tools are PR-shaped; none exercise the finished app, hold state across roles, or sign what they found. That window is the reason to move now.

Independence is a claim to earn: public methodology, open passport format, per-platform accuracy published, no training on customer apps without consent06 / 08
Team · why me

I spent my career building algorithms that were not allowed to fail. This is the same job.

Mike Bouskila · Founder

  • Software developer in a development unit of the Israeli Navy.
  • Algorithms developer at Mega Robot.
  • Full-stack development background.
  • Robotics algorithms and trading algorithms.

Naval systems, robots and trading engines do not get a second chance. Neither should the app a business runs on.

Built alone, before any outside capital

  • A generation engine that has produced 5,320 apps through production, with an owner area in every one.
  • The reliability layer: runtime autopsy, Proof Passport with 3,250 of 3,250 mutations refused, verified change, exactly-once money.
  • The discipline: 6,628 automated tests, disaster-recovery drills, and an evidence bundle where every claim carries its own proof.

First hires with this round

Two engineers on the verification fleet and detectors, one product designer, one Israel go-to-market lead. Named advisors from the verification and security community join a small bench.

Background stated by the founder · no ranks, dates or claims beyond it07 / 08
The ask · vision

$1.5M–$3M seed to prove the detectors on the world's apps and open the Verify door.

Weeks 1–3

Product proof

Run the full suite on the 37-category corpus plus 50 external Lovable, Bolt and v0 apps against a frozen answer key. Publish precision and recall per failure type. Hard gate.

Weeks 3–6

Design partners

10–20 agencies and inheriting teams, some paying, at least three repeating. Real apps, authorised scope only.

Weeks 5–8

Benchmark launch

Open skill, public benchmark with raw runs, a known-bad demo app, a sample passport and a limitations page.

Weeks 7–12

Verify Beta

Paid verification with fixes delivered in a branch, never in production. Create grows quietly as the Israeli beachhead.

Use of funds · 18–24 months

Engineering · verification fleet and detectors55%
Go-to-market · Israel, design partners, benchmark25%
Infrastructure and model costs12%
Legal, evidence-rights licence, reserve8%

The vision

Every app an AI builds will carry a signed passport of what it can do, what failed, and what was never tested. Pomela issues it.

Milestones for the next round: detectors generalise on external apps with published accuracy, a recurring continuous-passport revenue line, and two platform licences. Three exit lanes stay open by design: platforms, security, and AI labs.

Mike Bouskila · pomela.app · Confidential08 / 08