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.
Features
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.
Platform
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.
By link, per user or per team, with read-only or edit permissions. Users without an account receive an invitation.
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 Portico, protection extends to every single file.
For applications with no back end, which keep data in the browser alone: Portico stores it in the cloud, per user or shared, with no code changes. With Supabase the data stays in its database.
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.
A "Report" button on every application: bugs and requests reach Slack, Trello or Linear with page, user, screen and browser already filled in.
iPhone and Android apps and a web version: applications open inside Portico, side by side if needed, and remain available offline.
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.
Isolated spaces for companies or clients, with administrators, teams and a single account per user across organizations. Everyone accesses only their own content.
Archive applications not in use without deleting them. A log of sign-ins, releases and permissions for full traceability.
Errors and AI
Portico 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.
Orders · last 14 days
1,284opens
63people
94%error-free
The cart does not display products
The total is computed before the cart has loaded. 4 users out of 63.
✦ FixPull request open
Supabase Back-End
Most applications built with Lovable or Bolt run on Supabase. Portico recognizes the linked project, deploys the Edge Functions from the GitHub repository and checks that the required keys are set.
Orders · Supabase
4functions
v12checkout
1missing secret
send-email
The module npm:resend@9 does not exist: the AI suggests version 4 and drafts the prompt.
✦ DiagnosisCopy prompt
Databases
Not every application runs on Supabase. Portico 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.
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.
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.
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 the chosen fields are read, with explicit authorization. Portico 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
Portico decides who may open each application. Where the login is the platform's own, it handles it without changing the code.
With Supabase or Firebase, whoever opens a restricted application from Portico is already signed in to its login, with the same e-mail: no second password. The account is created if missing.
Portico 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 Portico gets the chosen level, before the session even starts.
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.
Optional for each Portico account: after the password, the code of an authenticator app. No external service.
We review every request and work alongside our first clients as they publish their applications.