Software development

Vibe-coded app to production

You've built something useful with AI tools, and now real people depend on it. We make it safe to run: a proper review, fixes for what's risky, and hosting and monitoring you can rely on.

What we check first

  • Who can see what

    Every page and API should check who is signed in and what they're allowed to see, on the server. AI-written code often checks this only in the browser, or forgets it on one route. This is the first thing we look at.

  • Secrets and keys

    API keys belong in the hosting platform's secret store, not in the code or the browser. We move them, and change any that were exposed.

  • Data and backups

    Where the data lives, whether it's backed up, and whether a bad change could lose it.

  • Dependencies

    Packages with known security problems, and a routine for keeping them up to date.

Then we make it production-ready

  • Tests where they matter

    Sign-in, payments and anything that changes data get automated tests, so the next change can't quietly break them.

  • Proper hosting and deployments

    Repeatable deployments from version control, with separate test and live versions.

  • Monitoring

    Errors and outages reach a person, rather than waiting for a customer to report them.

  • Accessibility and speed

    Pages that work with a keyboard and a screen reader, and load quickly on a phone.

Then we keep it running

Once it's live, we can look after it: updates, fixes and improvements, with the same checks on every change.

Software support and maintenance

Questions

Do you rewrite it from scratch?

Not unless we have to. We fix what's risky and keep what works, and tell you plainly if a part needs rebuilding.

Which tools' code can you work with?

Anything that ends up as normal code in a repository: React, Next.js, Node.js, Python and so on. If your tool keeps the code to itself, the first step is exporting it.

Can we keep building with AI tools afterwards?

Yes. We'll set things up so your changes go through the same tests and deployments as ours.

Tell us what you're building.

Email us about your project: what it needs to do, who it's for and when you'd like it live.