Staticbot logoStaticbot.dev
    Client app delivery

    Deliver AI-built apps into your clients’ cloud accounts.

    Build in Lovable, Base44 or a repository with coding agents. Deliver a working application into your customer’s accounts, and keep managing updates while they control their production infrastructure and data.

    6 min read
    By , Co-founder of StaticbotLinkedIn

    Ravel works on Staticbot’s migration platform, moving apps built with Lovable and Base44 onto Supabase and hosting their owners control.

    A client asks you to build a booking app, a customer portal or an internal operations tool. They want it running in accounts their business controls. Staticbot connects your development workflow to that delivery: customer-owned Supabase for data, AWS for static apps, or Cloudflare Workers for supported full-stack apps.

    Explore customer-owned app delivery

    Turn a working app into a customer deliverable

    AI tools make it practical for a small team or an independent builder to create useful software. Delivering that software brings another set of decisions: who holds the cloud account, where business records live, how each client’s configuration is managed, and who approves the next update.

    Staticbot’s agency workflow gives you a place to manage that work. A consultant can deliver a custom app to one company. A software vendor can maintain a reusable Lovable or Git application for several companies. A team building with Claude Code or Codex can use its repository as the source. Each engagement has a defined destination and an update process the customer understands.

    Client app delivery

    One source. Separate client accounts.

    Publish a release, then choose which client receives it.

    Your workspace → your clientsInteractive illustration

    Builder account

    Your Staticbot workspace

    Reusable Lovable / Git appYour source of application releases
    Private development · previews · demo
    DevelopTestPublish

    Source and client delivery projects are managed in this workspace.

    Selected release

    v1.3
    Review & apply
    per client

    Select a client to preview its delivery route. Each client keeps its own release schedule.

    Arrows carry application releases. Each client's users, bookings and files stay in its own Supabase project. AWS is an option for static sites and SPAs; supported server-rendered apps can run in the client's Cloudflare account. Client accounts shown are provider accounts; the agency manages the Staticbot delivery projects.

    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, use an authorized customer AWS account. For supported server-rendered apps, deploy a Worker into the customer’s Cloudflare account and attach their domain there.

    Their accounts

    Clients control their Supabase project and the AWS or Cloudflare account used for hosting, including provider access and billing.

    Their own data

    Each customer has independent users, records, uploaded files and application configuration.

    Their release schedule

    Apply a reusable app release to one client while another stays on its current version.

    Your agency manages the source and client delivery projects inside its Staticbot workspace. The connected Supabase, AWS and Cloudflare 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.

    A new Supabase-backed client starts with the application’s structure and functions in a separate empty project. Their users, business records and uploaded files grow in that project. Your development data and source secret values are kept out of the client release; each customer supplies their own configuration.

    Make each update a deliberate delivery

    1. Test your source version. Check the application and its database changes before publishing a selected release.
    2. Choose a customer. Prepare the changes for that client’s current version and settings.
    3. Review and approve. Inspect the proposed database and function changes, confirm the required configuration, and approve their application.
    4. Finish the deployment. Staticbot applies the release and deploys the client’s frontend. The installed version advances after the required backend and frontend work completes.

    That gives you a practical way to introduce an update to one customer and check the result before delivering it to another. A failed step remains visible for investigation and retry. You keep a separate version and configuration for each client as your customer list grows.

    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.

    Work with the customer’s infrastructure requirements

    Account ownership lets customers manage provider access and billing, choose their Supabase region, and keep their own domain. AWS S3 and CloudFront serve static websites and single-page apps. Cloudflare Workers run supported server-rendered applications and server functions. The backend remains a separate Supabase project with its own database, authentication and file storage.

    Some clients need a backend inside a private VPC or behind a firewall. Staticbot’s downloadable migration package can be applied from inside that network to a self-hosted Supabase. For ongoing releases in a private environment or a specific enterprise delivery process, discuss the target architecture with us so the deployment, access and operating responsibilities can be scoped to the engagement.

    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 the client’s Supabase destination and authorized hosting account: AWS for static apps or Cloudflare for supported full-stack apps.
    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.

    Keep building. Give clients control of their production.

    Build, migrate and maintain client applications from your agency workspace.