Liftport
Source inventory, parity proof and savings math — the guided Vercel exit cockpit you deploy and launch as your own SaaS.
Liftport moves a team's web application off an expensive managed host — Vercel, Netlify, Render — onto their own cheaper virtual server, and proves the move worked.
Parity is proved before the flip, not discovered after it.
Migrations fail in the fifteen minutes after the switch. Something that worked in staging does not work in production, and the rollback path turns out to be theoretical because DNS has propagated and the old environment was torn down to stop paying for it. The team spends the evening reconstructing a service under pressure, in front of the people who approved the move. Most teams respond by never migrating again, and the hosting bill they meant to fix becomes permanent.
- Post-cutover smoke check
- Guided cockpit wizard
The migration reports what it actually saved and when it paid for itself.
Infrastructure moves are sold on a number nobody revisits. The estimate justified the work; afterwards, the new bill lands in a different account, under different line items, and comparing the two honestly would take an afternoon that nobody has. So the saving becomes folklore — everyone believes it happened, nobody can produce it — and the next proposal to move something gets a harder hearing because the last one was never proved.
- Projected savings report
- VPS health + cost monitoring
Stop halfway on Tuesday and resume on Thursday without starting over.
Nobody migrates a production application in one sitting. The work is done between other work, across days, often by more than one person. A process that lives in someone's terminal history and a half-finished checklist does not survive that: state is lost, steps get repeated, and the second attempt is more dangerous than the first because nobody is sure what the first one already changed.
- Guided cockpit wizard
- Source inventory + attestation
The API cannot see everything, and pretending otherwise is how migrations fail at 2am. Sensitive environment values are not readable, and some routing lives in the repository rather than in the host's configuration. Those gaps are filled by a completeness checklist the operator attests to, and every line in the manifest records which it was: read from the API, or attested by a person.
That provenance stays attached to the manifest. When something is missing after cutover, the first question is which category it came from.
The cutover is not a leap. Before DNS changes:
It is calculated from the real bill being replaced, not from a list price.
It does not connect to the server and execute commands itself. That is a deliberate scope decision rather than an unfinished feature — direct execution puts a live production credential into an automated path, and the guided path removes that risk while a team is still deciding how far to trust the tool. Direct execution and a server-side agent are opt-in upgrades rather than the default.
Liftport checks the migrated server on a schedule and watches two things: health, and cost drift against the bill the migration replaced. Alerts arrive by email.
Cost drift is the interesting half. A migration that saved $400 a month in February is not necessarily saving it in August — the server grew, a second one appeared, the old host was never fully cancelled. Monitoring is what converts a one-time claim into a number that stays true.
Check cadence is one of the things plans scale: hourly on the mid tier, every fifteen minutes on the top one.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 50 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 65 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · languages · marketing_audience_members · marketing_audiences · migration_manifests · migration_plans · migration_runs · migration_steps · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · provider_prices · push_devices · report_templates · roles · savings_reports · scheduled_tasks · seo_meta · smoke_check_results · source_adapters · source_connections · subscriptions · target_generators · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · vps_health_checks · vps_targets · webhook_logs · webhooks
The chassis, and anything particular to this product. 5 required, 2 optional.
For the cockpit itself.
Postgres with row-level security, applied by the shipped migration scripts.
Both a one-time charge and recurring subscriptions, so the provider must support both.
Run completion, smoke-check results and drift alerts.
Migration runs and scheduled monitoring execute outside the request that starts them.
A token for whichever of the managed hosts is being migrated from. Supplied by the team, stored encrypted.
The virtual server being migrated to. Liftport never provides or runs it.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 122,924 lines across the application and its database, 65 tables defined by 85 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Liftport demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 3 of them: Operator, Account owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 76 page modules and 248 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, A payment provider, Email provider, A job queue, Source-host API access, A target server. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 85 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $199?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.