ShoredBook a 20-minute kickoff

Built it with Lovable, Bolt, Replit or v0?

Your app works. Something about it worries you.

A security warning, a migration that will not apply, a bug that keeps coming back, or an investor asking how solid it is. Give me one read-only day in your repo and I will tell you exactly what is open and what it costs to close. Fixed price. You keep building.

Free. If your app fits, the £550 day follows once it is paid.

Who this is for

You built it yourself, it has users or revenue, and you do not want a rewrite. You want the holes closed, the schema under control, and the confidence to keep prompting without reopening them.

Building with Cursor or Claude Code and shipping every day? The retainer is for you: it installs the conventions and gates so the next prompt cannot reopen a hole.

See the retainer

The £550 day

One day. One report. Then a fixed price to fix it.

For £550 ($750) I spend one day inside your repo and your Supabase project, read-only, and hand you a report that says exactly what is load-bearing and how well each piece is protected:

  • Every table: is row-level security on, and do the policy bodies actually restrict anything, or do they say “allow all” to make an error go away?
  • Anonymous and authenticated grants, exposed RPC functions, and any service-role key sitting in the browser bundle.
  • Secrets in the repo and in its history, not just the current commit.
  • Migrations: does the schema exist as code, or is production the only copy?
  • Tests and CI: what would actually turn red if someone broke the important thing.
  • Each risk graded by what it costs you if it goes wrong, with the cheapest adequate fix.

The report ends with a fixed total for the fixing work. Your £550 comes off that total if you go ahead. If you do not, you still have the report and a roadmap you can hand to anyone.

Report within two working days of access. Read-only.

Prices

The day

£550/$750

One read-only day inside your repo and your Supabase project. Report within two working days of access.

  • Full enforcement-tier report
  • RLS and secrets findings
  • Migrations state
  • Prioritised roadmap
  • Fixed quote for the fixing work

Hardening sprint

£4,500/$6,000

Up to ten days on the set that matters, shipped as reviewed pull requests while you keep building. The £550 is credited.

  • RLS policies that restrict something
  • Secrets out of the repo and its history
  • Migrations baseline and CI apply
  • Rebuild-from-empty gate
  • Tests and observability

Priced by what it closes, not by the day. If it takes fewer than ten days, the time left goes on the next items from your report. If the day shows the app needs more than ten days, you get a separate fixed quote before anything starts.

Keep-building-safely retainer

£3,000/$4,000

per month

For founders building with Cursor, Claude Code or a no-code builder who want the guard-rails to stay up. It installs:

  • Conventions file for your AI tooling
  • Agent-ready issue format
  • CI gates
  • Review loop
  • Monthly enforcement sweep

Larger apps quoted up to £4,000.

Prices in GBP and USD, excluding VAT, which is added for UK customers. EUR on request.

Paid in pounds or dollars, whichever your card is in. Invoice in the same currency.

How it works

  1. 1

    Kickoff call

    Twenty minutes, free. You tell me what is worrying you and I check your app fits the day. If it does, I send a payment link for £550 ($750); if it does not, I say so. Then read-only GitHub and Supabase access, and the day starts once it is paid.

  2. 2

    The day

    One day inside the repo and the database. If I find a live exposure I tell you immediately, before the report, at no extra charge.

  3. 3

    Report and fixed quote

    Within two working days of access you get the report and a fixed total for the fixing work, with the £550 credited if you go ahead.

  4. 4

    Sprint, you keep building

    Fixes go in as reviewed pull requests while you keep using your builder. The sprint leaves you the guard-rails so the next prompt cannot reopen the hole.

Evidence

The most recent rescue in detail, and the same work on the Next.js stack. The rescue took a founder-built app from open tables and leaked secrets to tested, migration-gated production, without stopping the founder building. Thirty years of the same kind of work follows.

Jason Brown
Jason Brown. Shored, Bagworth, Leicestershire.

30

years since the first rescue

226

pull requests merged in six weeks on the newest

0

rewrites. Every app kept its own codebase

A screenplay-analysis SaaS (React, Supabase, Deno edge functions, LLM pipeline)

Day one: enabled RLS, revoked anonymous grants, purged a committed env file and rotated its keys, baselined the production schema into migrations, moved the model calls server-side. Then a row-level-security test suite, mutation testing on the tests themselves, and a per-call quota chokepoint.

Every change landed as a reviewed pull request.

The same work on Next.js, Supabase and Vercel

Turning a hand-built schema into versioned migrations applied by CI on every merge, with workflows pinned by SHA. Server-side authentication and rate limits on routes that had none.

Every change landed as a reviewed pull request.

My own systems, so you can see how I build:

  • A production scheduler where Postgres row-level security is forced on every table and the app runs as a restricted role, so isolation holds even if the code is wrong.
  • A self-hosted security-testing agent runtime in C# with a policy engine the model cannot bypass, which is the engine behind the audit day.
  • A 2,080-commit product on Azure with LLM evals in CI, built with the autonomous issue loop I install for clients.

Thirty years of this

I have been the person called in when the system matters and the people who built it have gone since 1995. The rescue above is the newest; it is not the first.

NatWest Home Loans, 1995

A customer-communications system in Visual Basic and undocumented C++, the original developers gone. I made it maintainable, built a sane way to extend it, introduced source control, and trained the team so they never needed me again. Senior management wrote to thank the team.

Atos Origin, 1996 to 2015

Nineteen years on train ticketing under ISO 9001, including eight as a senior developer on WebTIS, the ticket-selling site used by East Coast, First Group and other operators, selling several million pounds of tickets a day, with an immovable launch date. Three of us also built a demonstration system in four weeks that won a multi-million-pound contract.

A US health-data platform, 2016 to 2023

Seven years designing and building the platform, a C# microservice back end, an Angular site and a mobile app, for children with learning difficulties, built to the US HIPAA privacy rules from the first commit.

A childcare app, 2026

Its platform, Xamarin, had reached end of life. Moved to .NET MAUI on .NET 10, with GitHub Actions pipelines building and shipping to both app stores, a test suite where there was none, and a token that was leaking into error logs stopped. Delivered with the same reviewed-pull-request loop I use on every rescue.

Since then

Conveyancing integrations for Connells Group on Azure with Terraform and queues, a flight-school app that records training outcomes and takes payment through Stripe, and my own AI products on Azure.

Microsoft Certified Solution Developer since 2002. B.Eng. in microelectronics, Newcastle. Private pilot for twenty-five years, which is where I learned that checklists beat confidence.

Questions

Will you break anything?

The audit is read-only. Fixes only happen after you accept a written quote.

Do I have to stop building?

No. You keep using your builder. The fixes go in as reviewed pull requests, and the sprint leaves you with the guard-rails so the next prompt cannot reopen the hole.

What if the report says it is fine?

Then you have a report that says so, with the evidence, which is what an investor or acquirer will ask for.

Do I pay before we have spoken?

No. The first step is a free twenty-minute call. If your app fits the day I send a payment link for £550, and the day starts once it is paid. If it does not fit, I tell you on the call.

Can you fix it today if it is bad?

If the day finds a live exposure, I tell you immediately with the exact policy or key rotation, before the report, at no extra charge. Closing it is a ten-minute job you can do yourself, or I can do it for a fixed quote.

Start with twenty minutes

A free kickoff call to check your app fits. Then one read-only day inside your repo and your Supabase project, a report within two working days, and a fixed price to fix what matters, with the £550 credited.

Calls in UK and European hours, and in US hours from East Coast mornings to Pacific evenings.