Home/Services/Prototype to Production
Prototype Production Review · $890 fixed · 5 business days

The vibe coding agency for prototype to production.

Gigabit is a vibe coding agency for the step after the prototype. A senior engineer reviews the app you built with Lovable, Bolt, Replit, Cursor or Claude Code: security, data model, performance and deploy. In 5 business days you get a graded report and a fix plan. $890 fixed, credited in full to a build started within 60 days.

The gap

What does a vibe coding agency do after the prototype?

A demo has to work once. A product has to work every time, for every user. The work after a prototype is less about new features and more about the engineering a demo never needed.

AreaThe demoIn production
AccessOne account, the founder'sEach user reaches only their own rows and files
KeysWhatever key made it workOnly the public key in the browser; secrets on the server
FailureRefresh and try againErrors reach an engineer before a customer
ReleasesEdit and publishStaging, migrations and a rollback
CostFree tier, ten usersA known cost per user and a cap

None of that means the prototype was a mistake. It is cheaper to find the gaps before launch than after the first incident, and the review finds them for a fixed price before you commit to anything larger. To check the basics yourself first, start with our vibe coding security checklist. Still choosing a builder? Read Lovable vs Bolt. Starting from scratch instead? That is a job for an MVP development company.

What the review checks

What the Lovable app security review checks.

Four areas: security, data model, performance and deploy. Security comes first because it is the one that ends a launch. The Supabase points are cited to Supabase's own documentation.

Security

Row-level security off, or too broad

Supabase says a table in an exposed schema without RLS is readable and writable by any role with a grant on it, and that a policy written to anon using (true) gives every unauthenticated visitor read access. We read every table and policy, flag policies that rely on user_metadata (Supabase warns against that too), and check whether one signed-in user can read or change another user’s rows.

The wrong key in the browser

The anon or publishable key is meant for client code and only reaches what Row Level Security allows. The service-role or secret key bypasses RLS, and Supabase says never to put one in a browser, a shipped app or source control. We check the built bundle, the environment files and the repository history for it.

Auth and sessions

Sign-up, sign-in, email confirmation, password reset, session expiry and refresh, and whether role checks run on the server or are only hidden in the interface.

Storage bucket permissions

Which buckets are public (anything in one is publicly accessible), and whether the policies on private buckets let a user reach only their own files.

Input validation and rate limits

Server functions and API routes that accept input without checking it, and sign-up, login or paid AI calls that anyone can repeat without a limit.

Secrets in the repository

Third-party keys (payments, email, model APIs) committed to the code or its history, or called from the browser. Anything exposed goes first in the fix plan, marked for rotation.

Data model

Schema and migrations

Whether the tables will hold up under real use, whether constraints and foreign keys exist, and whether schema changes go through migrations or are made by hand in a dashboard.

Backups

Whether backups exist, how far back they go, and whether anyone has ever restored one.

Performance

Queries and page weight

Missing indexes, queries that run once per row, and oversized responses and pages on the main paths through the app.

What it costs to run

Hosting, database and model or API spend per user, and where a cap belongs. A prototype that is cheap for ten users can be expensive at a thousand.

Deploy

Environments

Whether development and production share one database or one set of keys, whether there is a staging environment, and whether a release can be rolled back.

Error monitoring and logs

Whether a failure reaches an engineer before it reaches a customer: error tracking, logs you can search, and alerts someone reads.

Who owns it

Whether the repository, hosting, database, domain and third-party accounts sit with your company or with a personal login.

How it runs

From read access to a fix plan in 5 business days.

Written so your own engineers, another team or we can act on it straight away.

Day 1

Access

You give us read access to the repository and the project's database and hosting dashboards. We make no changes.

Days 1–5

The review

A senior engineer works through the four areas above against your real configuration, not a questionnaire.

5 business days

The report

Graded findings and the fix plan, in writing. Yours to keep whether or not you work with us afterwards.

Within 60 days

Fix it, with anyone

Fix it yourself, with another team, or with us. If you start a build with us within 60 days, the $890 is credited in full.

Graded findings

Every finding with a severity from critical to low, where it sits in the code or configuration, and the evidence for it.

A fix plan with effort

The findings in the order to fix them, each with an effort estimate, and which ones block a launch.

Keep, repair or rebuild

Our call on the codebase as a whole, with the reasons written down. The three outcomes are below.

What it is not: the review does not include fixes, which are a separate engagement quoted from the fix plan, and it is not a penetration test or a compliance certification. If the app runs its own AI agents or model calls on private data, that is an AI security assessment, From $8,900, fixed.

Keep, repair or rebuild

The call the report ends in.

Every codebase lands in one of three groups. You hear which, and why, before you have committed to more than the review.

Keep and harden

When

The data model is sound, the code is readable and the gaps are the usual ones: access rules, tests, error handling, deployment.

What it means

Most of the work is additive. This is the common case when the prototype was built carefully.

Repair

When

The product works but one layer does not hold: usually the schema, the auth model or a tangle of duplicated logic.

What it means

We replace that layer and keep the rest. Users see the same product.

Rebuild

When

Fixing it would cost more than writing it again: no consistent structure, no safe way to change one part without breaking another.

What it means

The report says so, with the reasoning written down. The prototype becomes the specification, which is still worth a great deal.

Pricing

What does a review of a vibe-coded app cost?

Published prices for checking a Lovable app, each read on the provider's own page on 15 November 2026. Scopes differ, so compare what each one looks at, not only the price.

ProviderPublished priceWhat it covers
LovableBuilt-in pentest, powered by Aikido$100 per testAikido's agents attack the live app, at what Lovable calls the same depth as a traditional pentest; one to four hours, per Lovable's announcement of 24 March 2026.
Rapid DevelopersLovable security audit$1,000 fixedFor a standard Lovable app, read-only, about 5 business days: auth, API and backend, database and RLS, secrets, a ranked fix plan. Fixes are extra; the fee is credited to them.
Foresight MobileLovable to production (UK)£95 review; fixes £999–£1,999The review covers payments, business logic, search visibility and what stays tied to Lovable, credited to the next paid work. Fixes and store launch are a separate fixed price.
GigabitPrototype Production Review$890 fixed5 business days: security, data model, performance and deploy, a graded report, a fix plan and a keep, repair or rebuild call. Credited in full to a build within 60 days. Fixes are quoted from the plan.

An automated pentest tests the running app from outside. A review reads the code, the database policies and the deploy setup, and ends in a plan. Fixes are priced from that plan, because nobody can price fixes to a codebase they have not read.

Fix and launch, with us

Embedded AI Teams · $2,900–$5,900 / engineer / mo

A dedicated development team works through the fix plan in your repository. 2–4 week trial, no lock-in, first pull requests by Day 5.

Only one workflow to fix?

AI Quick Win Sprint · $5,900 · 3 weeks

One automation, scoped, built and deployed for a fixed price. How the sprint runs is on our AI automation agency page.

AI features to run after launch?

Managed AI Operations · From $1,290/mo

Monitoring, eval regressions and model-change response on a retainer: managed AI services.

Proof, and its limits

What we can show you, and what we cannot yet.

Joining a codebase that already exists

A Series B HR-tech company embedded three Gigabit engineers in a live product with a seven-engineer team. First pull requests in 5 days, and sprint velocity went from 34 to 78 points over the first three months. Read the staff augmentation case study.

Shipping a first product that holds

A logistics SaaS reached production in 11 weeks for $48,000, with zero critical bugs at launch and 78% automated test coverage, and had 14 paying customers by month 6. Read the SaaS MVP case study.

We do not yet have a published case study of reviewing or taking over an app that was built with an AI builder. The two above show the parts the work is made of: working inside someone else’s code, and getting a new product to a launch that holds. When the first one is public it will be linked here. Other services are on our software development services page.

Prototype Production Review FAQ

Questions founders ask first

What is a vibe coding agency?

A vibe coding agency is a software team that builds with AI coding tools, or takes over apps that founders built with them in Lovable, Bolt, Replit, Cursor or Claude Code. Gigabit's part is the step after the prototype: the Prototype Production Review, $890 fixed, then fixing and launching the app if you want us to.

How much does a Lovable app security review cost?

At Gigabit, the Prototype Production Review is $890 fixed and takes 5 business days. It covers security (including Supabase row-level security, exposed keys and auth), the data model, performance and deploy, and you get a graded report and a fix plan. The fee is credited in full to a build with us started within 60 days. Fixes are not included: they are a separate engagement, quoted from the fix plan.

How is the review different from Lovable's built-in pentest?

Lovable announced penetration testing powered by Aikido on 24 March 2026, at $100 per test, run by AI agents against the app. The Prototype Production Review is a senior engineer reading the code, the Supabase policies, the data model, performance and the deploy setup, and it ends in a fix plan and a keep, repair or rebuild call. The two look at different things, so running the pentest as well is reasonable.

Can a vibe-coded app go from prototype to production?

Often, yes. A prototype built with an AI app builder or a coding assistant usually proves the idea and the interface. What it tends to lack is what a demo never needs: access control that holds, tests, error handling, monitoring, a rollback path and a cost ceiling. Those can be added to a sound codebase, and the review tells you whether yours is one.

What does the review check in a Supabase app?

That row-level security is on for every table in an exposed schema and that no policy is broader than it should be; that the service-role or secret key is not in the browser, the bundle or the repository history; sign-up, sign-in and session handling; storage bucket permissions; input validation and rate limits; secrets committed to the code; backups; error monitoring; and whether development and production are separated, with a release you can roll back.

What happens after the review?

You decide. The report and fix plan are yours, so you can fix the app yourself, hand it to another team, or have us do it. With us, fixing and launching is done by an embedded team at $2,900–$5,900 per engineer per month, with a 2–4 week trial, no lock-in, and a build started within 60 days gets the $890 back as a credit.

Will you rewrite my app or keep the code?

We keep what holds. The report puts the codebase into one of three groups: keep and harden, repair one layer, or rebuild. If the answer is rebuild, the report says so in writing, with the reasons. We do not start a rewrite quietly.

Who owns the code and the accounts?

You do. The review only needs read access, and any later work happens in your repository and your cloud accounts. Part of the review is checking that the repository, hosting, database, domain and third-party accounts sit with your company and not with a personal login.

Go deeper

From the field notes

Prototype Production Review

Find out what stands between your prototype and a launch.

Tell us what you built and what it runs on. In 5 business days you get a graded report and a fix plan, for $890 fixed, credited in full to a build with us within 60 days.