Build in your agency. Deliver to your clients' own infrastructure.

Give each client a deliverable they control

A booking system for a clinic, a customer portal for a consultancy, an internal tool for a local business: your client needs a working application and a clear home for its data. Deliver the app to a Supabase project in their account, with their own database, authentication and file storage. For static sites and SPAs, you can also deploy hosting into an authorized customer AWS account.

Your agency manages the source and client delivery projects inside its Staticbot workspace. The connected Supabase projects and customer AWS accounts belong to the client. This gives your agency a place to operate the delivery while the client controls the infrastructure that holds their business data.

Build once, deliver separately

For Lovable and other Git-based applications, maintain a reusable source in your agency workspace. Develop and test there, publish a selected release, then review and apply it to individual client targets. New Supabase-backed clients start with the application's schema and functions in an empty project. Hosting-only Git applications can use this delivery workflow too.

Suppose you build a booking application for a clinic, a studio and a consultant. They share the application, but each has its own backend, domain and settings. When you add appointment reminders, the clinic can receive the new release first. The other two keep their current version until you choose to update them.

Releases deliver application code, tracked database changes and functions to the selected client. Customer records stay in that customer's backend. You can keep developing your source without sending every unfinished change to live customers.

Or migrate the app a client already built

Agency work also starts with an existing Lovable or Base44 application. Import that client's project, connect a Supabase destination you are authorized to use, and run a test migration. Review the findings and working preview with the client, then plan the live move around their users and business.

Your agency provides the white-glove service: understand the application, coordinate acceptance and cutover, and maintain it afterwards. Staticbot runs the migration and deployment workflows. Use the live migration process for apps with active users, and Continuous Sync for ongoing changes to the migrated project.

Let clients follow their delivery

You can invite a client to view its specific deployment, running version and live URL. If the engagement calls for it, Collaborator access lets them submit permitted application secrets for your team to review and apply. That access is scoped to their project; your source development and other clients stay separate.

This uses Staticbot's separate collaboration feature. Collaboration gives people access to work together or follow a project. Agency delivery sends an application to a client's infrastructure. Use either on its own, or both for a client engagement.

Start with one customer

1. Import your reusable Lovable/Git app into your agency workspace, or start a migration for an existing client app.
2. Connect an authorized Supabase destination in the client's account. For static hosting, you can also use an authorized client AWS account.
3. For reusable app delivery, choose Project Settings → Deliver to clients, publish a validated release, and review its application to the client target.
4. Deploy on the selected hosting option and the client's domain. Invite the client to follow the project if useful.

Existing migration and hosting options apply. Self-service migrations are currently free, managed sites and apps count toward your workspace's hosting plan, and client-owned infrastructure is billed by its provider. Optional Supported Migration adds human review and troubleshooting for one migration. See the agency pricing note.