You built it on Replit. Here's how it runs for your company.
We move the code into your company's Git and deploy it into a cloud account registered to your company. There the platform, not the code Replit's agent wrote, handles company sign-in, access and keys, and there's no public replit.app address. We also review every change before it goes live.
For whoever built the app on Replit, and for the IT person asked to put it into production.
Updated 22 October 2026
Pushed from Replit's Git pane, or a ZIP download of the project.
Zerops, or AWS on request. Registered to your company, not to us.
Replit's database is PostgreSQL. It moves with pg_dump and pg_restore.
What people ask when a Replit app becomes a company app
Word for word from Replit's community forum, with our short answers.
“Is there a way to protect the myapp.replit.app url? When I connect it to my domain (...) the app is still available through myapp.replit.app”
The app has no public address. The only way in is the platform's sign-in, and the replit.app copy gets unpublished.
“I simply want user to be able to access my app only without having to create a replit account, is that possible?”
Colleagues sign in with their company account through your identity provider (for example Microsoft Entra ID, Google Workspace or Okta), outside people with a password. Nobody needs a Replit account.
“Could really use a one-button deploy to push a Replit app to an enterprise stack behind a firewall.”
Not a button, and not your own servers. We deploy into your company's cloud account, reachable only through sign-in.
“my monthly replit bill has been consistently hovering around $500–$1000 (...) it's almost entirely driven by constant agent usage top-ups and keeping a few key deployments running.”
Servers are paid to the cloud provider by usage and the AI runs on your own plan. We charge a one-off takeover and a monthly fee per app, never per user or per hour.
What changes when the app leaves Replit?
Screens, logic and data stay; sign-in, keys and deployment move to the platform.
Comes along as it is
- The code and its commit history, pushed from the Git pane to a private GitHub repository in your company's organisation.
- The data. Replit's database is PostgreSQL, and Replit's own guide moves it with
pg_dumpandpg_restore.
Has to be set up again
- Secrets never leave the Replit project, so keys are copied by hand or issued again, into the cloud.
- Sign-in. Replit Auth uses Replit accounts; the platform takes over with company accounts and passwords.
- Files in App Storage are downloaded and uploaded to storage in your account.
- Connectors to other services, and your custom domain.
- Agent history and checkpoints stay on Replit; their commits come along in Git.
public apps from Lovable, Replit, Base44 and Netlify found by RedAccess. Around 5,000 held sensitive data, often with no sign-in.
Try it yourself
Open your replit.app address in a private browser window. Whatever you can see without signing in, anyone can see.
How does an app get from Replit into production?
The Replit app keeps running until the new one is ready. How long it takes depends mostly on the data; the offer says exactly.
- 01
Scoping call
free · 30 minWe check what the app uses from Replit (database, Replit Auth or Clerk, App Storage, connectors). Within days you get an offer with scope, timeline and price.
- 02
Code to your GitHub
you, in a few clicksYou push from Replit's Git pane to a private repository, ideally in your company's organisation, or send a ZIP. We don't need your Replit account.
- 03
We go through the code
part of the takeoverKeys in the code, sign-in, database queries and where data goes. We discuss the findings with you.
- 04
Small changes
part of the takeoverThe platform takes over sign-in from Replit Auth and keys move into the cloud. Screens and logic stay.
- 05
A test copy of the data
part of the takeoverSo the new version can be tried with real data while the Replit app keeps running.
- 06
Deployment into your account
one-offInto a cloud account registered to your company, on Zerops, or on AWS on request. No public address, separate test and production.
- 07
Switch-over and unpublishing
from go-live · monthlyOn an agreed day you unpublish on Replit, we copy the final data and point your domain at the new app. Every later change goes live after our review, with a report.
What we look at in the repository
.replit How Replit runs and publishes the app. Replaced by the deployment. replit.nix System packages. We carry over what the app needs. DATABASE_URL Pointed at the database in your account. package.json Or requirements.txt. Whether dependencies install outside Replit. When is Replit Pro or Enterprise enough?
Replit answers some of this itself. (Replit Pro replaced the former Teams plan.)
What Replit offers
- Pro and Enterprise: access controls on a published app.
- Enterprise: SAML single sign-on and SCIM provisioning, with roles mapped to your groups.
- Enterprise: admins can require private deployments, security scans before publishing, and every change pushed to Git first.
- Enterprise: audit logs to your SIEM and a choice of region, including the EU. Otherwise apps run on Google Cloud in the US.
- Enterprise is bought as an annual credit commitment or pay-as-you-go.
Replit is the better fit when
- your people build and run everything inside Replit and want to keep it that way;
- IT wants SAML and to manage builders from its identity provider;
- automated scans and publishing policies are enough, without a person reviewing changes.
Fabrika is the better fit when
- the app should run in your company's cloud account, outside the tool;
- you want a person to review every change and someone who answers for running it;
- apps come from Claude Code, Cursor, Lovable or an agency too, and should all run by the same rules.
When isn't Fabrika for you?
- A public service for thousands of customers, with open sign-up and payments. Fabrika is for company apps.
- A few people use the app, nothing important depends on it, and restricting access on Replit Pro is enough.
- Your IT requires Azure, Google Cloud, your own servers behind a firewall or SAML-only sign-in. Fabrika runs apps on Zerops, or on AWS on request, and connects company accounts through OIDC (for example Microsoft Entra ID, Google Workspace or Okta).
- You want the code checked once and will run it yourselves. A one-off audit is cheaper.
Can we keep building on Replit afterwards?
It isn't a standard route yet. Replit syncs with GitHub, but its preview runs outside the platform and sign-in no longer goes through Replit. Ask us and we'll look at your app.
Much like with Replit's agent, people can now also edit the app through their own Claude or ChatGPT, for now only on Zerops. We're still verifying that in production.
What works for certain today
You carry on in Claude Code, Cursor or Codex, or we develop the app. Every change goes live through our review.
What people ask about Replit apps
Does the Replit app keep running while you work on it?
Yes, until switch-over day, when we make the final copy of the data. Unpublishing doesn't delete the Replit project, so if something went wrong, the old app could be published again as it was.
What if a platform error wipes the last stable version?
The code lives in your company's Git, so the last version doesn't vanish with a tool. Backups and restore we set up with you, to the extent you need.
Where will the data live?
Replit publishes apps on Google Cloud in the US; Enterprise can choose another region, including the EU. On Fabrika the data sits in a cloud account registered to your company, so we are your only supplier. Zerops is a Czech company with a data centre in Prague.
Who looks after the app when the person who built it leaves?
A colleague, a developer or we carry on: the repository belongs to the company and we handle operations and review. Closing their company account ends their access.
A colleague brought us the app and IT is supposed to deploy it. Where do we start?
With the scoping call, ideally with both of you. For IT we've written up what the platform handles and the answers to a typical security questionnaire: Security.
Show us your Replit app.
Half an hour and a link to the app or the repository. We'll tell you what the move involves, what happens to the database and sign-in, and whether it makes sense for you at all.