App Drive

Features

Every application published, protected, monitored and connected to the others.

The tools to take applications built with AI into production and keep them reliable over time: publishing from any source, controlled access, data, monitoring and error diagnosis, without touching the code.

Request an invite See pricing

Platform

The tools to publish, share and govern applications.

Any source

A web address (Lovable, Bolt, Replit, v0 or your own domain), a Vercel or Netlify project, a GitHub repository or a .zip archive. With GitHub, every push is published automatically.

Sharing and permissions

By link, per user or per team, with read-only or edit permissions. Users without an account receive an invitation.

Protection for shared apps

With "Login required" a shared application opens only for authorized users and teams, from the app and the browser. No login system to build or configure: for applications hosted on App Drive, protection extends to every single file.

Cloud data Pro

For applications with no back end, which keep data in the browser alone: App Drive stores it in the cloud, per user or shared, with no code changes. With Supabase the data stays in its database.

Errors and AI Pro

Errors collected automatically and grouped by AI into issues with their cause. The fix is delivered as a prompt for Lovable or Cursor, or as a pull request on GitHub.

Overview Tailored

The numbers of your applications on one page: today's orders, this month's revenue, open tasks. Set up from the app, with no code; flows pass new data from one application to another. The assistant proposes cards and flows from a written request, without seeing the data. Supported sources: Cloud data, Supabase, PostgreSQL, Firebase Firestore.

Contextual reports Pro

A "Report" button on every application: bugs and requests reach Slack, Trello or Linear with page, user, screen and browser already filled in.

Mobile and desktop

iPhone and Android apps and a web version: applications open inside App Drive, side by side if needed, and remain available offline.

Company brand

Logo, name and colors in the app and on the login pages, and a domain of its own for every application (app.client.com) with an automatic certificate. For agencies, a dedicated space per client.

Organizations and teams

Isolated spaces for companies or clients, with administrators, teams and a single account per user across organizations. Everyone accesses only their own content.

Archive and activity log

Archive applications not in use without deleting them. A log of sign-ins, releases and permissions for full traceability.

Connected applications · Custom plans

Applications talk to each other, with no integrations to build.

Applications built with AI start out separate, each with its own database. App Drive connects them: it reads the data where each application stores it, brings it together in a single Overview and passes new data from one application to another.

  1. Connect the data

    App Drive's cloud data, Supabase, PostgreSQL, Firestore: through a dedicated access, with the explicit authorization of whoever manages the application.

  2. Choose cards and flows

    In the app, with no code: a list, a total, a count filtered by period; when new data arrives, the action to take in another application.

  3. Everyone sees their own picture

    The Overview shows each person only the applications they can open, on smartphone and desktop, with the organization's brand.

Examples

  • An order placed in the Shop creates the picking task in the Warehouse.
  • A new contact from the website becomes an appointment in the CRM.
  • Today's deliveries, this month's revenue and open tickets, on one page.
  • New data also sent to Slack, Zapier or Make through a signed webhook.
  • When an order becomes "shipped", the matching delivery is updated.
  • Only orders above €100 start the flow: the others never leave the application.
  • The website contact form or a Stripe payment starts a flow through a dedicated, secret address.
  • An AI agent, such as Claude, answers "how many orders came in today?" by reading the applications' data.

Guarantees

  • Only the chosen fields are read; data changes only in the flows that update a record, in the chosen fields, and is never deleted.
  • Of what changes, only an encrypted fingerprint is kept, never the value.
  • Cards read the data when opened: no copy is kept.
  • Every delivery of a flow is logged, with retries on errors.
  • The assistant proposes cards and flows from the request and the field names, without access to the values.
  • AI agents access only the authorized applications through the MCP protocol, to read or to add new data; access can be revoked at any time.

Errors and AI

Failures detected first, with the fix already prepared.

App Drive monitors the applications your team builds: it tracks usage and errors on every page with no code changes. AI identifies the cause of failures and prepares the fix.

  • Build diagnosis. The causes of a failed build explained clearly, with the missing variables already proposed and the code fix ready on GitHub.
  • Error analysis. Errors and reports grouped into issues, with severity, probable cause and affected users.
  • Fix. A prompt for Lovable or Cursor, or a pull request on GitHub. On the next version App Drive verifies that the issue is resolved.
  • Instant rollback. If a new version causes more errors than the previous one, App Drive offers to return to the last stable version.
  • E-mail alerts. Failed builds and new errors reach the app's owner, even with App Drive closed.

Supabase Back-End

The application's back end, in step with every push.

Most applications built with Lovable or Bolt run on Supabase. App Drive recognizes the linked project, deploys the Edge Functions from the GitHub repository and checks that the required keys are set.

  • Project recognized. The Supabase address is found in the build or in the code: just confirm it.
  • Functions on every push. After each build only the changed Edge Functions are deployed, with no CLI or setup.
  • Secrets checked. Keys the functions read but are not set yet are flagged; the AI says where to get them and the values stay on Supabase.
  • Database migrations. The database changes written by the AI tool are explained in plain words and applied in order, each in a transaction; after every push, an alert when new ones arrive.
  • Diagnosis. When a function fails to deploy, the AI explains why and drafts the prompt for your development tool.

Databases

Data stays where the application keeps it.

Not every application runs on Supabase. App Drive also connects to the platform's PostgreSQL database or Firestore: tables and collections feed the Overview and flows without copying the data and without changing the code.

PostgreSQL

Neon, Railway or a company server. The app proposes the SQL for a dedicated user, read and insert only; the connection is always encrypted and the password stays encrypted on the server.

Firebase Firestore

Connected with the key of a dedicated Google service account. Collections become cards and flows; a new document can start a flow to another application.

Checks and fixes

Security rules that expired or are open to everyone, missing indexes, Cloud Functions in error, Prisma migrations not applied, foreign keys without an index: flagged in plain words and, where possible, fixed from the repository in one tap.

Only what is needed

Only the chosen fields are read, with explicit authorization. App Drive adds rows or documents; it changes existing ones only in the flows that update a record, in the chosen fields, and never deletes them.

Access

Who gets in, and with which level.

App Drive decides who may open each application. Where the login is the platform's own, it handles it without changing the code.

Automatic sign-in

With Supabase or Firebase, whoever opens a restricted application from App Drive is already signed in to its login, with the same e-mail: no second password. The account is created if missing.

Access levels

App Drive finds where the login keeps each person's role (a column, a field, a custom claim) and lets you change it from the app. Whoever enters from App Drive gets the chosen level, before the session even starts.

Complete profile

If the platform needs more details (the company, a code), the person fills them in a form at the first opening. With Firebase the fields to ask are suggested from the users collection and chosen by whoever publishes the application.

Two-step verification

Optional for each App Drive account: after the password, the code of an authenticator app. No external service.

An invite-only beta, with support in going live.

We review every request and work alongside our first clients as they publish their applications.

Request an invite See pricing