Application and runtime
Assess framework, language, build, start process, container readiness, health checks and runtime assumptions.
Platform-specific capabilities
Capture serverless and edge functions, buildpacks, preview deployments, cron jobs, workers, routing and caches.
Data and persistence
Evaluate databases, volumes, object storage, uploads, queues and their export or synchronisation paths.
Configuration and integrations
Add secrets, variables, domains, OAuth callbacks, webhooks, email and external APIs to the dependency map.
Target models
Compare managed Coolify, Docker, Kubernetes or other platforms on German, European or customer-controlled infrastructure.
Staging and production
Record the Git process, environments, approvals, rollback and intended separation in the target design.
Cutover and risk
Structure data change rate, DNS, permitted outage, rehearsal, rollback point and acceptance criteria.
Operations after the move
Account for monitoring, backups, updates, logs, ownership and a possible co-managed split.
PaaS Exit Review: plan a sound migration from Vercel, Heroku and other platforms
WZ-IT inventories the platform capabilities in use, evaluates suitable target models and develops a traceable migration path. You receive a technical decision basis before infrastructure is built or the production application is changed.
Starting point
When the PaaS Exit Review is useful
- The target between Coolify, Docker, Kubernetes or another model is still open
- Vercel, Heroku, Railway, Render, Fly.io or Netlify provides several implicit platform capabilities
- Cost, data location, portability or operating ownership must be compared first
- Several services, databases, workers, volumes or environments must be assessed together
- An internal team needs a reliable roadmap or a basis for an implementation proposal
A deliverable, not a preliminary call
A reliable basis for the target decision and migration proposal
The review separates straightforward portability from genuine replatforming. Dependencies, data paths and operating capabilities become visible before a timeline, target platform or outage window is promised.
Source and dependency map
Application, builds, runtimes, functions, data, storage, jobs, domains, secrets and integrations are captured as one connected path.Evaluated target options
Coolify, Docker, Kubernetes and German, European or customer-controlled infrastructure are compared against suitability and operating needs.Concrete migration path
You receive the sequence, central risks, rehearsal and cutover logic, and a basis for a subsequent implementation proposal.
Source-specific guides and the complete PaaS exit checklist.
Open PaaS migration knowledgeReview scope
What must be clarified before a PaaS exit
The review covers the complete platform path. The depth of each area depends on the source, application and material available.
Effort factors
The entry price requires a review that can be scoped clearly
- Number and coupling of applications, repositories and platform projects
- Availability of configuration, exports, cost and architecture data
- Depth of platform-specific functions, edge runtimes and data products
- Amount of code analysis or experimental target testing required
- Large datasets, low outage tolerance and multiple regions
- Special security, high-availability or compliance requirements
Process
From the current state to an actionable exit decision
The review ends with a documented result. Migration and subsequent operations remain separate decisions and engagements.
- 01
Define the question
Agree the source, application, reason, target criteria and material available.
- 02
Capture the platform path
Inventory resources, dependencies, data paths, deployment and current operating capabilities.
- 03
Evaluate targets and risks
Compare suitable target models and classify portability, adaptation or replacement for each capability.
- 04
Hand over the exit plan
Present the recommendation, migration sequence, review gates and next commercial step in a documented form.
What we need for initial assessment
- Source platform, application and reason for the intended move
- Repository and framework overview without immediate credentials
- List of platform services, databases and integrations in use
- Current environments, broad sizes and known operating requirements
- Target preferences or criteria such as location, control, cost and availability
Entry engagement
PaaS Exit Review from €1,490 excl. VAT
Pricing starts at €1,490 excluding VAT for one clearly bounded application and platform path. Before engagement, we confirm the question, required material and specific review scope.
The review is not a migration, penetration test or complete Production Readiness Audit. If the code itself needs deeper assessment, we scope that step separately.
All prices are net and exclude statutory VAT. The offers are addressed to businesses.
PaaS Exit Review
For teams that need to clarify targets, dependencies, risks and a realistic migration path before implementation.
Factors that determine price
- Number of applications and platform resources
- Source platform and specialist capabilities in use
- Data, storage and integration scope
- Code or configuration analysis required
- Number of target models to compare
- Availability, security and operating requirements
After the review
Review, migration and operations remain separate decisions
You can execute the exit plan internally, continue with another partner or engage WZ-IT for migration and ongoing operations.
PaaS and cloud exit
Migrate the application, data and deployment process with rehearsal, cutover and rollback point.
View migrationProduction Readiness Audit
Assess code, auth, data, security, tests, deployment and operational readiness in depth.
View application auditManaged Coolify Hosting
Operate a Git-based target platform with monitoring, backups, updates and a personal contact.
Explore CoolifyFrequently asked questions about the PaaS Exit Review
Scope, price, platforms, outcome and next steps
- The PaaS Exit Review starts at €1,490 excluding VAT. The specific price depends on the number and coupling of applications, source platform, data, specialist capabilities, material available and the number of target models to assess.
- The PaaS Exit Review assesses platform dependencies, target models and the migration path. The Production Readiness Audit assesses the application itself across code, auth, data, security, tests, deployment and operational readiness. Both questions may matter for unknown inherited code.
- No. A clearly bounded application with few platform services can be proposed directly as a migration. The review is useful where the target, portability, data paths, specialist capabilities or effort cannot yet be determined reliably.
- Common sources include Vercel, Heroku, Railway, Render, Fly.io, Netlify, AWS Amplify, Cloudflare Pages or Workers and DigitalOcean App Platform. What matters is not the product name alone but the capabilities the application actually uses.
- No. Coolify is one possible platform and Hetzner one possible infrastructure provider. Depending on the application, we also assess Docker, Kubernetes, other German or European providers, customer cloud environments and on-premises targets.
- You receive a documented assessment of source dependencies, evaluated target options, central risks, a recommended migration sequence and technical guardrails for rehearsal, cutover, rollback and subsequent operations.
Reviews & projects
Software projects with reliable outcomes
Proof for modernization, API extension, architecture, deployment and ongoing operations.
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT
Read client reviews
- Modernize your legacy software
- Ship your prototype to production
- Design an open-source AI architecture
- Plan a sovereign open-source stack
- Secure your Proxmox & backup setup
- Modernize your infrastructure - sovereign
- Integrate a local AI solution
- Cut cloud cost - up to −81%
- Build a high-availability Proxmox cluster
- Virtualize with Managed Proxmox
- Get collaboration fully managed
- Connect sites and clusters securely
Request a review
Which platform path should be assessed before migration?
Describe the source, application, known dependencies and purpose of the review. We first confirm whether the review is the right starting point and how the scope should be bounded.
