blog

A proposal to prevent mass security incidents like Lovable's

Stephen Sisk

I'm building Skape, an app platform that's secure by default. This essay argues that platforms like Lovable need security built in rather than scanned for, and shows how Skape does it.

Lovable is a service that allows anyone to build websites with AI. In a recent Lovable security incident discovered by Crissy Field GmbH, 24,664 websites had their databases publicly accessible. What was exposed varied by site, but some of the information exposed included passport numbers, birth dates, invoices, contracts, names, and email addresses.

This is emblematic of a larger problem with the overall idea that we can give tools designed for engineers to non-coders and expect good results when they code with agents. In 2026, if something is accessible on the internet, you cannot make any security mistakes. The challenge for coding platforms is that in order for apps to be really useful, users want them to be accessible everywhere and to everyone.

Lovable's response to the security issues raised in the incident was that users need to be paying attention to security scans and fixing the issues raised. Security issues have gotten more and more complex over time, and it is a stretch for a platform to expect that non-developers will spend time worrying about whether their app is susceptible to subtle but dangerous security attacks or that they will understand the tradeoffs of the mitigations that agents will propose. When we have more people building, with less security knowledge, we increase the likelihood of attacks succeeding.

While I appreciate that Lovable is doing their best, instead of trying to scan for security issues (which is a game of whack-a-mole) we need to give non-technical users a platform where security is the default. Folks deserve a place where they can be creative and build without worrying about subtle security issues.

Introducing Skape

Like Lovable, Skape is an app platform where you can quickly build apps. However, Skape has security built into the platform. Apps are treated as untrusted by the platform, with users granting permissions for what apps can do.

Skape has multiple layers of security that help prevent your data getting leaked:

Would Skape have prevented the Lovable security incident?

None of this data would have been reachable by a public internet security scan if the apps had been built on Skape. Skape's security measures mean that app creators get secure defaults - most users' data never would have been accessible at all because only invited users can see their data. The caveat discussed below is that some of the apps couldn't have been built on Skape.

In the case of apps where different users have different permissions and some data is meant to be hidden from others, business logic will always determine who can see what, so humans and agents will always have to be involved in that code (regardless of the platform). But the fact that users can only run defined queries means that we've massively simplified the review.

Tradeoffs & Caveats

Skape is built to support collaborative apps where a single user works with data or small to medium groups of users work together with data. It can't support public forum style apps or apps where anyone on the internet can submit info for a website owner to review. For published apps, anyone can open the app - but since your copy of the app is private to you and anyone you invite, anonymous users can't see it, and new users get their own private space. For many of the affected apps, I suspect the creator didn't need to have everyone working with the same database and exposing their users' data wasn't worth it.

Additionally, moving security into the platform means that if there is a security issue in the platform, all apps would be affected. But would you rather have a security feature like sharing implemented by software engineers focused on building just that feature vs thousands of non-developers who are trying to quickly get a feature out the door on their vibe coded app? I think that concentrating the risk in the platform is the right tradeoff for this environment.

Skape makes it more fun to build apps

What's exciting to me is that since I don't have to spend time worrying about security in the apps I'm building on the platform, I find it very freeing - I can just focus on having fun building the apps.

Skape makes building apps startlingly simple - it only takes a minute to connect your agent and get started creating an app.

Try it out now

Get started building right now - not sure what to build? Is there an app you use every day that you'd love to slightly tweak? Try building your own version on Skape.

Build an app in 10 minutes

Anyone who can has Claude Code or Codex can build apps on Skape. We provide the hosting, and we send instructions to your coding agent on how to develop apps following current best practices.

Never used Claude Code before? Start here
Don't have an AI coding tool yet? Install Claude Code

Follow the official quickstart guide to install Claude Code on Mac or Windows. Once installed, run claude from any terminal to start a session.

Can you use the free ChatGPT / Gemini / Claude chat tools to write an app?

In theory you can, but it's frustrating and if you really intend to build an app we recommend that you go ahead and spring for the subscription.

The free models are hard to work with for complex tasks. Building a working app takes a lot of code that has to hold together. The free tiers use smaller, cheaper models, and they tend to produce apps that almost work — broken pieces, bugs they can't find, and rewrites that undo things that used to work. This subtle "it's almost but not quite good enough" is almost worse than just failing at the task outright.

They can't connect to Skape. Chat tools can't connect to Skape directly, so nothing is automatic: you copy code out of the chat window, paste it into files by hand, and upload them yourself. Every change means doing that again. An AI coding tool with a Skape connection just writes the files and ships the new version for you.

What we recommend: a paid Claude plan — the $17/month Pro plan is more than enough for building Skape apps, and it includes Claude Code, which connects to Skape directly. Once you've got the app set up the way you want it, you don't need to keep the Claude subscription to use apps here on Skape.

I have an existing app - can I port it?

Yes! Skape supports porting existing apps over. Your agent will be able to do the porting once it's connected to Skape.

  1. Sign up for an account

    All we need is an email address.

    We'll send you a 6-character code.

  2. Connect your agent to Skape

    Copy this prompt into Claude Code, Codex, or your agent of choice. It carries a private URL your agent uses to create and update your apps.

    Read https://skape.run/skape-sys/agents/{secure token here}/prompt.md and follow it to build apps on skape.
  3. Tell Claude to build your app

    Then ask for your app:

    > on Skape, build me a photo sharing app for my family
  4. Visit your working app on your phone or desktop!

    Your agent gives you the link when it's done:

    https://family-photos.skape.run

    Your app is private by default. You can share it with friends and colleagues, or publish it so anyone can use it.