1:1 matching
Cloud Jetorbit is not AWS or any other provider, so we replicate each service you use as closely as possible. Your team keeps working with the same technology.
managed service / infrastructure migration
Move your infrastructure without changing the technology
For setups that span several servers: clusters, load balancers, CI/CD pipelines and internal VPNs. The Jetorbit team replicates each component on Cloud Jetorbit, then moves it over in stages.
- Kubernetescontainer orchestration
- Traefikload balancer & ingress
- JenkinsCI/CD
- Rediscache
- RabbitMQmessage queue
- PostgreSQLdatabase
- VPNinternal access
01 / approach
Your setup is replicated, not redesigned
Until the migration is done, the old provider keeps billing you. So the move is prepared first and then carried out in stages, while the old setup keeps serving your customers until DNS changes.
Topology and cost up front
Before anything moves, we draw up the topology on Cloud Jetorbit together with an itemized cost.
In stages
Services move one at a time and their data is replicated. User traffic is redirected only after the internal dry run is complete.
02 / migration process
The order we work in
This is the same order we used to move Inkanteen off AWS. How many services are tested and moved per stage depends on your setup.
- 01
Assessment
We list the services running at the old provider and the topology you want to reach.
- 02
Design & cost
The Cloud Jetorbit topology is drawn up with an itemized cost for your approval.
- 03
Trial run
A few services are brought up on Cloud Jetorbit first for testing.
- 04
Migration & data replication
Services move in stages and their data is replicated before DNS changes.
- 05
Internal dry run
The team confirms everything works before user traffic is redirected.
- 06
DNS switch
DNS is pointed to Cloud Jetorbit, then data that changed during the process is reconciled.
- 07
Managed
After the move, the Jetorbit team maintains the infrastructure through Managed Service.
03 / where it goes
Where your infrastructure moves to
One setup can use both, for example application nodes on Cloud VPS and the database on a Dedicated Server.
Cloud VPS
For application nodes, workers and clusters. Turbo and Classic plans in the Jakarta datacenter.See Cloud VPS →Dedicated Server
Full physical resources for databases or heavy workloads. The Managed Server plan (Rp750,000/mo) already includes migration.See Dedicated Server →Load balancing, HA & clustering
Set up to match your architecture as part of the Managed Service scope.See what is covered →
04 / case study
Inkanteen: from AWS to Cloud Jetorbit
Inkanteen has ceased operations and no longer subscribes to Jetorbit services. We keep the story of its migration as a picture of how the Jetorbit team carries out Managed Service work.
05 / migration form
Tell us about the setup you run today
Which services you use, at which provider, and which parts must not go down. From there we draw up the topology and an itemized cost.
Prefer to talk it through? Discuss on WhatsApp.
Need a formal quote for procurement? Request a written quote.