Main content
Deploy & Migration

From repository to cloud, with the cost on the table first

Varcio Deploy & Migration analyses a GitHub repository, compares deployment paths across AWS, Azure, Google Cloud, Oracle and hybrid, generates AWS-ready infrastructure code, and runs the migration control plane that executes and tracks the move.

  1. AnalyseGitHub repo
  2. CompareCosted paths
  3. BlueprintTerraform / OpenTofu
  4. PlanReport
  5. DeployTracked run
Cost is on the table before anything is built.
5Deployment paths compared: AWS, Azure, Google Cloud, Oracle and hybrid
TerraformOr OpenTofu blueprints, generated from the repository
3Screens: assessment, migration and cloud access
TrackedEvery run has a full event stream and a report
Workflow

Analyse, compare, generate, plan, run

Migration and greenfield deployments commit you to a cost structure for years. This makes the costed comparison the default instead of the exception.

  1. 01

    Analyse the repository

    Select a GitHub repository and branch. Varcio infers what the application needs to run: runtime, dependencies, data services and network requirements.

  2. 02

    Compare deployment paths

    See AWS, Azure, Google Cloud, Oracle and hybrid options side by side, each costed, so cost is weighed against the operational character of each path.

  3. 03

    Generate a blueprint

    From the chosen path Varcio generates AWS-ready infrastructure code as Terraform or OpenTofu. You can edit the blueprint before anything is planned.

  4. 04

    Plan and read the report

    Run a plan and read the per-blueprint deployment report. This is where cost and resource implications become concrete.

  5. 05

    Check it can deploy

    A preflight asks whether the blueprint can deploy right now to every place it names, and a readiness assessment runs before any run.

  6. 06

    Execute and watch

    Execute the run as a tracked deployment with a per-run event stream, then validate the live cost against the plan in Overview and Cost Center.

Capabilities

What Deploy & Migration includes

Planning, infrastructure code, preflight and execution in one module.

Your repository
  • Runtime
  • Dependencies
  • Data services
  • Network needs
Deployment paths
  • AWS
  • Azure
  • Google Cloud
  • Oracle
  • Hybrid

GitHub repository analysis

Branch selection and inference of runtime, dependencies, data services and network needs.

Cross-cloud path comparison

AWS, Azure, Google Cloud, Oracle and hybrid, with cost planning built into the comparison.

Blueprint generation

AWS-ready blueprints in Terraform and OpenTofu, with blueprint editing and plan generation.

Deployment reports

A per-blueprint report, with an architecture figure drawn for the deliverable.

Existing-estate discovery

Per-provider discovery of what already exists, so a plan accounts for the current state and the VPCs and subnets a deployment can actually run in.

Tracked runs

Execute a run with a full event stream, so you can follow and review every step.

Cloud Access

What your clouds are actually allowed to do, measured rather than assumed

Most deployments fail on permissions. Cloud Access finds that out before you try.

  • Read accessPowers analysis, discovery and assessment
  • Permission preflightReports exactly which permissions are missing
  • Execution role (optional)Verified and stored separately from read access

Cloud Access runs a permission preflight against your real connected accounts and reports what each connection can and cannot do, rather than trusting what the role is supposed to allow.

Because Varcio separates read access from execution access, you can use planning, assessment and the rest of the analytical product on read-only credentials, and grant execution only when you want to deploy or remediate.

Connection model

  • AWS: IAM AssumeRole with a per-customer External ID, no stored access keys
  • Azure: service principal, GCP: service account, OCI: API signing key, all encrypted at rest
  • Separate read and execution roles, verified independently
  • Preflight that names exactly which permissions are missing
After you deploy

Deployments register themselves for monitoring and cost

What you deploy is watched and costed from the first day.

  1. DeployedLive release
  2. MonitoredService Monitoring
  3. InventoriedWith scan lineage
  4. Cost checkedPlan vs live

Service Monitoring

A successful live release registers every place it went, with what the cloud needs to read it back, so the new service is watched automatically.

Inventory

The resulting infrastructure appears in Inventory with scan lineage.

Cost validation

Compare the live cost with the plan in Overview and Cost Center, and let policies, budgets and anomaly detection apply from day one.

FAQ

Questions, answered

What does Deploy & Migration do?

It analyses a GitHub repository, compares deployment paths across AWS, Azure, Google Cloud, Oracle and hybrid with costs, generates AWS-ready infrastructure blueprints in Terraform or OpenTofu, and runs and tracks the deployment or migration.

Does it generate infrastructure as code?

Yes. Blueprints are generated as Terraform or OpenTofu, can be edited, planned and reported on, and are then executed as a tracked run. Generating real infrastructure code means the plan and the deployment cannot drift apart.

Which clouds can I compare?

AWS, Azure, Google Cloud, Oracle and hybrid options are compared and costed. Blueprint generation is AWS-ready today.

Do I need write access to use it?

Analysis, comparison and planning work on read-only connections. Executing a deployment needs an execution role, which is verified separately from the read-only role.

Which plans include Deploy & Migration?

Pro, Business and Enterprise.

Cost the move before you make it

Connect GitHub, analyse a repository and compare clouds. Free trial, no credit card required.