Cloud Computing

GCP Migration Strategy: Tools, Risks, and Cost Considerations

Guy Brodetzki
Mar 25, 2026
·
6 min read

Key Takeaways

  • Strategy before servers: A GCP migration strategy starts with workload assessment, dependency mapping, and a separate data migration plan before anything moves.
  • Costs go beyond compute: Factor in redesign labor, dual-environment overlap, and egress fees. Build optimization into the plan from day one, not after go-live.
  • Business decision first: AI capabilities, cost flexibility, and operational resilience are the real drivers, not just a technical checkbox.

The difference between a smooth cloud migration and a painful one almost always comes down to what happens before anything moves.

‍

Most organizations know they need to get to the cloud. But McKinsey research found that up to 75% of cloud migrations go over budget. The reasons tend to repeat: unclear dependencies, surprise costs, and workloads moved without a plan for how they'd run on the other side. Teams treat migration as a logistics problem when it's really an architecture problem.

‍

A strong Google Cloud Platform (GCP) cloud migration strategy changes this by starting with workload assessment, dependency mapping, and cost modeling before a single server gets touched. When the foundation is right, the execution becomes predictable.

‍

Explore how to plan and execute a Google Cloud Platform migration, what each phase requires, how data is handled, and what shapes the overall cost.

Why Organizations Are Prioritizing Google Cloud Platform Migration

‍

Moving to GCP gives teams access to capabilities that are hard to build and sustain in-house.

‍

AI and data capabilities

Google Cloud's AI and machine learning ecosystem, including BigQuery, Vertex AI, and TPUs, gives organizations a ready-made platform for analytics and ML workloads. For teams training models or deploying generative AI, GCP's infrastructure is already optimized for it.

‍

Cost flexibility

GCP's pay-as-you-go model shifts IT spending from large upfront purchases to operational costs that scale with usage. Sustained-use discounts and committed-use programs add budget predictability on top of that.

‍

Operational resilience and compliance

GCP runs on a globally distributed network with multi-region redundancy and self-healing infrastructure, delivering near-100% uptime for mission-critical services. On the compliance side, default encryption, Zero Trust architecture, and GDPR/HIPAA-aligned certifications make it a fit for regulated industries.

What Defines a Strong GCP Cloud Migration Strategy

A solid GCP migration plan starts with understanding your current environment, defining how each workload should move, and planning for potential risks.

‍

The 6 Rs framework

Not every workload gets the same treatment. The 6 Rs give you a way to categorize each one based on its technical profile and business value.

  • Rehost (lift and shift): Move as-is to Compute Engine VMs. Fastest path, fewest cloud-native benefits.
  • Replatform (lift and optimize): Move with minor adjustments like shifting a database to Cloud SQL or containerizing for GKE.
  • Refactor (re-architect): Rewrite for cloud-native patterns. Highest long-term ROI, biggest upfront effort.
  • Repurchase: Replace legacy apps with cloud-based SaaS alternatives.
  • Retire: Decommission apps that no longer serve a purpose.
  • Retain: Keep certain workloads on-prem due to regulatory, latency, or complexity constraints.

The value of this framework is that it forces a decision for each workload rather than applying a blanket approach.

‍

Related Content: The Top Cloud Cost Cutting Platforms

‍

Workload assessment and dependency mapping

You can't migrate what you don't fully understand. 

‍

Automated discovery tools help catalog servers, databases, and infrastructure components, then map their dependencies. That dependency graph is what lets you group workloads into migration waves so interconnected systems move together instead of breaking apart mid-transfer.

‍

Risk planning

Configuration drift, network bottlenecks, and data corruption are the kinds of problems that surface during execution if they aren't identified during planning. 

‍

Strong strategies address failure modes upfront. That means building rollback procedures, testing in isolated environments, and assigning priority levels to risks based on severity and likelihood. The goal is to make the final cutover a non-event.

Core Phases of a Google Cloud Migration

A Google Cloud Platform migration follows five phases. Each one builds on the last, and skipping ahead is where most projects start to break down.

‍

Phase 1: Assessment

Start by taking inventory of what you have. 

‍

Automated discovery tools like the Google Cloud Migration Center catalog your on-prem assets, including servers, databases, and storage. 

‍

From there, benchmark current performance (latency, throughput, error rates) so you have a baseline to measure against. This is also where you build your total cost of ownership (TCO) comparison between your current setup and projected GCP spend.

‍

Important questions to ask:
  • What servers, databases, and storage systems are currently in production?
  • What does our current environment cost to operate annually?
  • Which workloads are candidates for migration and which need to stay on-prem?

‍

Phase 2: Planning and foundation

This phase is about building what Google calls the "Landing Zone," your secure, scalable foundation in GCP. That includes setting up a resource hierarchy (Organization, Folders, Projects), defining IAM roles based on least-privilege access, designing VPC networking, and establishing connectivity to your existing environment through VPN or Cloud Interconnect.

‍

Important questions to ask:
  • How should our resource hierarchy be structured for billing and policy control?
  • Who needs access to what, and at what permission level?
  • How will we maintain connectivity between on-prem and cloud during the transition?

‍

Phase 3: Execution

Move in waves, starting with non-critical applications or pilot workloads to validate the strategy. Use continuous background replication to keep the target environment in sync with the source. Orchestration tools handle launch sequencing, so applications come online in the right order.

‍

Phase 4: Validation

Before the final cutover, test everything in isolated environments. Clone workloads into separate VPCs for functional and performance testing. Verify data integrity through row counts, checksums, and schema checks. Confirm that the target environment meets or exceeds the baseline you set during assessment.

‍

Phase 5: Post-migration optimization

Once workloads are live, the work isn't done. 

‍

Rightsize instances based on actual usage data, transition rehosted VMs toward managed services like Cloud Spanner or GKE, and set up continuous governance using tools like Active Assist for ongoing recommendations on cost, security, and performance.

‍

The common mistake is treating Phase 5 as optional. Optimization should be built into the plan from the start, not added on after go-live.

Designing a Successful Cloud Data Migration Strategy

Data migration is not the same as application migration. It needs its own plan, tools, and validation process. A cloud data migration strategy should cover where your data is going, how it gets there without downtime, and how you prove it arrived intact.

Database migration paths

Google Cloud offers managed options depending on your workload type, including:

Service Best for Availability SLA
Cloud SQL MySQL, PostgreSQL, SQL Server relational workloads 99.99%
Cloud Spanner Global-scale apps needing strong consistency 99.999%
AlloyDB High-performance PostgreSQL workloads 99.99%
Firestore NoSQL and document-based use cases 99.999%

‍

Choosing the right target service early prevents rework later. Match each database to the service that fits its access patterns and scale requirements.

‍

Minimizing downtime

The Database Migration Service (DMS) uses Change Data Capture (CDC) to replicate data in real time. 

‍

Your source database stays fully operational throughout the process. Every insert, update, and deletion gets captured and synced to GCP in the background. 

‍

When you're ready, the cutover is a simple repoint of the application to the new cloud endpoint. Schedule the final switch during off-peak hours with a documented rollback plan ready.

‍

Data integrity validation

Google's open-source Data Validation Tool (DVT) automates the comparison between source and target databases. It runs checks at three levels: table level (row counts and filters), column level (schema and data type verification), and row level (hash comparisons for bit-level accuracy). 

‍

Catching a data discrepancy after cutover is significantly more expensive than catching it before.

‍

Storage transfer

For non-database data like file systems and object storage, the Storage Transfer Service handles most scenarios. 

‍

For massive datasets where bandwidth is a constraint, Google's Transfer Appliance ships to your data center, gets loaded with up to several hundred terabytes, and returns to Google for upload.

‍

Cost Considerations in a GCP Migration Plan

Migration costs don't stop at your monthly cloud bill. A realistic GCP migration plan should account for the full picture: what it takes to get there, what it costs to run, and where the savings actually come from.

‍

Direct migration costs

Infrastructure redesign is often the biggest upfront expense. Dependency mapping, Landing Zone design, and re-architecture work all require skilled labor, and the scope scales directly with the complexity of your environment. 

‍

There's also the overlap period. Running dual environments during migration and validation is unavoidable, and it temporarily increases IT spending until the source environment is decommissioned.

‍

Egress fees

Moving data out of an existing cloud provider used to be one of the most painful cost surprises.

‍

Since 2024, Google, AWS, and Microsoft have started waiving egress fees for customers exiting their platforms permanently. The catch: it requires approval and a defined migration window, usually around 60 days.

Google Cloud incentives

Google offers several programs to lower the barrier to entry. The Rapid Migration and Modernization Program (RaMP) provides service credits based on incremental usage, plus funding for specialized partners to help with assessment and roadmap development. 

‍

For startups, the Google Cloud for Startups program offers up to $350,000 in credits over two years for companies building AI-focused products.

‍

Long-term optimization

This is where the real savings show up. GCP's pricing model includes several built-in mechanisms for reducing spend over time. 

  • Sustained-use discounts: Automatic reductions for workloads that run consistently through a billing cycle.
  • Committed-use discounts (CUDs): Significant reductions for one or three-year commitments.
  • Spot VMs: Steep savings for fault-tolerant batch processing.
  • Cold storage tiers: Archive or Coldline pricing for data that's rarely accessed.

‍

Cost category Strategy Tool
Egress fees Apply for exit fee waivers GCP Support/case review
Compute waste Rightsizing and auto-scaling Active Assist/Managed Instance Groups
Storage costs Lifecycle management and tiering Cloud Storage Lifecycle Policies
Migration labor Leverage RaMP partner funding RaMP Program
Initial consumption Consumption-based service credits Google Cloud for Startups/RaMP

Start Your GCP Migration With a Clear Plan

The difference between a migration that delivers value and one that drains budget comes down to preparation. 

Most teams know what they want from GCP: better AI capabilities, cost flexibility, and infrastructure that scales without constant manual work. The challenge is getting there without the delays, overruns, and surprises that slow down the majority of migration projects.

‍

InfrOS simplifies GCP migrations using an intelligent cloud infrastructure optimization engine that designs, simulates, and deploys cloud architecture across AWS, Azure, and GCP. It analyzes over 1,000 infrastructure parameters to generate optimized, deployment-ready configurations, cutting months of planning down to days. 

‍

Get a migration plan built on optimized, deployment-ready architecture. Book a demo to see how InfrOS gets you there.

FAQs

How long does a typical Google Cloud Platform migration take?

It depends on scope. Small projects with a few apps can wrap up in 2 to 6 weeks. Medium-scale moves typically take 2 to 4 months. Large enterprises with 50+ applications and complex legacy systems often need 6 to 18 months.

‍

What workloads are most complex to migrate to GCP?

Legacy monoliths like large ERP systems and heavily customized Oracle databases. Anything built on proprietary hardware, custom middleware, or with circular dependencies between services will need significant refactoring or a phased wave approach.

‍

How can teams reduce downtime during cloud data migration?

Use continuous replication through the Database Migration Service with Change Data Capture so the source stays live. Test in isolated VPCs before cutover. Schedule the switch during off-peak hours with a documented rollback plan ready.

‍

Are Google Cloud migration tools sufficient for enterprise environments?

Google's native tools (Migration Center, Database Migration Service, Migrate to Virtual Machines) cover most use cases. For multi-cloud or non-standard setups, teams often supplement with third-party options for added flexibility.

‍

When should optimization planning begin in a GCP migration plan?

During assessment, not after go-live. Set performance benchmarks and rightsizing targets before the move. Build cost controls like budget alerts and resource tagging into the Landing Zone from day one.

‍

Keep on reading

InfrOS
InfrOS Joins the Microsoft for Startups Pegasus Program
Naor Porat
Nov 19, 2026
·
6 min read

InfrOS is excited to announce its acceptance into the Microsoft for Startups Pegasus Program. This collaboration provides InfrOS with access to powerful AI tools, Azure credits, and a global customer network to help scale faster and smarter.

‍

We’re excited to welcome InfrOS to the Microsoft for Startups Pegasus Program. This initiative gives select startups access to Azure’s cutting-edge AI models, enterprise-grade security and privacy, and unique go-to-market support to accelerate growth. Through Pegasus, startups can build fast, scale smart, and sell more by tapping into the full power of Azure and the Microsoft ecosystem

- Tom Davis, General Manager, Microsoft for Startups

‍

Look out for more exciting news in the near future!

‍

Cloud Architecture Design
Why Configuration Drift Breaks Production and How Teams Prevent It
Guy Brodetzki
Nov 12, 2026
·
6 min read

Cloud environment changes with every single modification. Various new services are added; changes in configurations occur; infrastructure changes to accommodate various load capacities. Such modifications are necessary, but they involve opportunities for the inconsistency within the environment.

‍

The configuration that was performed during the staging phase will never appear in the production phase, while the fix to the issue in the production phase will never appear in the infrastructure configuration.

This process is referred to as the configuration drift and the understanding of its reasons and prevention is needed to provide consistency of the cloud environment.

Key Takeaways

  • Configuration drift is described as a state where the implemented infrastructure does not conform to the configuration required anymore, especially after making manual changes, temporary fixes, and inconsistent deployments.
  • The staging and production environments should have consistent configurations and operations despite having different resource capacities and size requirements.
  • With infrastructure as code, automation testing, and deployment processes, teams can avoid recurring drift.
  • Detecting drift involves detecting inconsistencies, and teams have to understand their effects before solving them.
  • InfrOS is an application that enables teams to assess architecture decisions before implementing them and consistently check for infrastructural consistency.

What Is Configuration Drift, and Why Does It Happen?

Configuration Drift is a term for the gap between the expected and actual configurations of the infrastructure. Consider, for example, an engineering team deploying an application through Terraform. The configuration specifies all the resources required by the application: servers, network, storage, database, and security settings.

‍

Everything corresponds to the expected configuration at first. However, after a couple of weeks, an engineer adjusts one of the network rules to fix a problem. Another engineer scales up a database in order to improve its performance. Both adjustments might be necessary, yet none of them are captured in the initial infrastructure configuration. The resulting environment deviates from the expectations of the engineering team.

‍

It raises uncertainty: the next deployment can undo the changes made, and engineers looking through the configuration files can rely on the outdated settings. The term configuration drift is widely used in the cloud environment due to the frequent changing of infrastructure. Resources are being added, resized, replaced, and reconfigured according to the evolving application. Moreover, one should differentiate configuration drift from the architectural drift.

‍

The former relates to the settings of individual resources while the latter implies deviation of the whole infrastructure structure, dependencies, and behavior. Both make cloud environments harder to manage, but architectural drift often requires broader changes than simply restoring individual settings.

Why Does Infrastructure Drift After Every Release?

Releases cause modifications in both applications and the underlying infrastructure. Ideally, this should be the case regardless of whether development, staging, or production environments are being referred to. In reality, this does not always apply.

‍

Sometimes, a developer makes a change in the staging environment to get the release working properly. The application gets through its tests but the modification in the infrastructure is never added to the deployment package. By the time the application is deployed to production, it acts differently due to the lack of the required setting. It may also occur the other way around, where a manual change was made in the production environment and nothing gets changed in staging.

‍

There are several reasons for that.

- Manual changes: Engineers modify resources directly through cloud consoles instead of updating the infrastructure definition.

- Environment-specific settings: Different variables, permissions, or networking configurations create differences that are difficult to track.

- Emergency fixes: Temporary changes made during incidents remain active without being documented.

- Inconsistent deployment processes: Different teams use different scripts, tools, or procedures to update infrastructure.

‍

These issues become more common as environments grow and release frequency increases. However, drift is not an unavoidable consequence of frequent deployment. It becomes a recurring problem when teams lack a consistent way to define, validate, and promote infrastructure changes. The goal is to make every release predictable, regardless of how often changes occur.

How Do I Keep My Cloud Environments in Sync?

Keeping cloud environments aligned does not mean making development, staging, and production identical. Production may need more compute capacity, stricter security controls, or higher availability than staging. These differences are expected. What matters is that differences are intentional, documented, and managed through the same process.

There are several principles that make this possible.

‍

Use one consistent infrastructure definition

The practice of infrastructure as code enables teams to define resources via version-controlled configurations instead of creating resources manually. A common template and/or module will ensure that each environment is following the same architecture design, while specific environmental variables will control any difference between the environments, such as resource size. This will make comparison easier and minimize any risk of undocumented modifications.

‍

Deploy through consistent processes

Changes to infrastructure should occur via a reusable deployment pipeline. Teams should not deploy changes directly to production; rather, they should promote changes after review via testing and staging. Whenever possible, the same version of the application artifact and infrastructure configuration should be used. This allows you to guarantee that what has been tested is what will be deployed.

‍

Treat staging as a meaningful production test

The process of staging must reflect those dependencies, assumptions, and infrastructure behaviors that are present in production. It is not always required to have the same capacity, but the major differences must be known. In case the staging environment has different network policies or lacks vital services, tests in this environment mean little for production.

‍

Continuously check for differences

Even with consistent deployment processes, unexpected changes can occur. Regular drift detection helps teams compare actual infrastructure against approved definitions and investigate differences before they affect future releases. Together, these practices create an environment where changes remain controlled without slowing down development. For more on creating consistent infrastructure through better architecture practices, see our guide to Shift-Left Cloud Infrastructure Design.

What Guardrails Prevent Configuration Drift?

Guardrails are rules and processes that help teams make safe infrastructure changes without requiring manual oversight of every decision. They should prevent common mistakes while allowing engineers to respond when something genuinely needs to change.

Several guardrails are particularly useful.

‍

Version control and code reviews

Infrastructure definitions should be stored in version control, with changes reviewed before deployment. This creates a record of what changed, why it changed, and who approved it.

‍

Access controls

Restricting direct production modifications reduces the risk of undocumented changes. Emergency access can remain available, provided changes are reviewed afterward.

‍

Policy checks

Automated policies can identify configurations that violate security or operational requirements, such as missing encryption, excessive permissions, or unapproved resource locations.

‍

Automated drift detection

Regular comparisons between deployed infrastructure and approved definitions help identify unexpected changes early.

‍

Deployment approvals

Important infrastructure changes should pass defined checks before reaching production. Higher-risk changes may require additional review.

‍

Guardrails should also account for legitimate exceptions. A temporary production fix may be necessary, but it should be documented and either incorporated into the approved configuration or reversed when no longer needed. The objective is not to block change. It is to make infrastructure changes visible, consistent, and easier to manage. For a broader perspective, see our article on Cloud Governance Tools for Engineering Teams.

How Do I Validate Changes Before Promoting Them to Production?

Environmental consistency is but one piece of the puzzle. It’s equally important that teams feel confident in the behavior of new changes. An effective staging release does not necessarily imply a successful production deployment. The process of validation must start prior to any infrastructure modifications.

1. Review the proposed change

Start by identifying which resources, configurations, and dependencies will change.

Infrastructure as code tools can show proposed modifications, helping engineers identify unexpected replacements or configuration differences.

‍

2. Check policies and requirements

Validate the change against security policies, capacity requirements, and operational constraints. This helps prevent configurations that may work technically but violate important requirements.

‍

3. Test in staging

Deploy the proposed change to a representative staging environment. Check application functionality, connectivity, dependencies, and relevant performance requirements.

‍

4. Evaluate the broader impact

A change can work in isolation while creating problems elsewhere. For example, moving a service to another region may affect network latency, data transfer costs, or recovery behavior. These effects should be considered before production deployment.

‍

5. Promote the approved change

After successful validation, push the approved configuration and application artifacts according to the deployment process defined previously. Watch for any issues with the release and have fallback or recovery options in place. The main idea behind this is straightforward: infrastructure changes must be validated prior to being introduced into production, not only after an issue occurred.

What Should I Use If My Architecture Drifts Every Release?

If there are unexpected differences because of changes in infrastructure with every release, then the first thing to do would be finding out where these differences have originated from. Resource level configuration drift, Infrastructure as Code, automated deployment pipelines, and drift detection form a robust base for this process. Using tools like Terraform will enable you to manage approved configurations and find differences in the managed infrastructure.

‍

But recurring drift can also mean that there is a more serious problem at hand. If engineers are continually increasing capacity, changing service connections, and network configurations, then the architecture itself might not meet the demands of the application anymore. In such cases, reverting to previous settings might be a short-term solution but the same problem will keep recurring every time there is a new release.

‍

With the help of InfrOS, engineering teams can develop, evaluate, and validate infrastructure architectures before putting them into practice. This is done by assessing architectural alternatives in terms of cost, performance, reliability, security, and complexity. Using Evolving Architecture™, InfrOS facilitates continuous architectural assessment in case of changes in workload, requirements, and cloud capabilities. This is in addition to the configuration management approach that assesses only the consistency of the resource with its initial configuration. With InfrOS, engineering teams can also assess the compliance of the architecture with its requirements. This is useful for companies facing architectural challenges on an ongoing basis. You can read more about developing these capabilities in our guide to the Enterprise Architecture Maturity Model.

FAQ

What causes configuration drift in cloud environments?

Configuration drift is typically caused by manual changes, patching, inconsistent deployment practices, and environment-specific configuration management that is not being consistently maintained. Configuration drift can occur as well because various teams implement varying approaches for managing the same infrastructure environment. As environments evolve, inconsistencies arise which create uncertainty during deployments.

‍

How do you detect infrastructure drift?

Infrastructure drift is recognized through a comparison of the actual state of the resources and the approved infrastructure definition. Tools like Terraform and cloud native configuration drift detection solutions help recognize any deviation. Routine automated monitoring assists organizations in recognizing drift before it impacts production operations, while further validation aids in determining if the modification poses a security or performance threat.

‍

Is all configuration drift bad?

It is not always bad. There could be valid business reasons for changing certain configuration parameters, such as scaling a database or adjusting networking in order to solve a particular issue. However, what makes infrastructure drift risky is the fact that the modification has no documentation or is not validated against the approved requirements.

‍

How often should you run drift detection?

It is recommended to carry out drift detection often and ideally within the context of automated deployment workflows. Important infrastructures would do well checking for drift after updates to their infrastructure, releases, and at periodic intervals. It really depends on how frequently their infrastructure changes and how tolerant of risks they are willing to accept.

‍

Can configuration drift be prevented entirely?

The level of configuration drift can be minimized to a large extent, but avoiding it completely may not be possible when you are working with dynamic cloud infrastructures. You can avoid drift through IaC practices, pipelines, automated validation, and security restrictions. Nevertheless, there will always be exceptions. Configuration drift does not merely consist of changes in configuration. This is a production risk only if an organization cannot see where things got changed, how they were changed, and if everything in its environment is operating according to expectations.

‍

By ensuring consistency in infrastructure definitions, validating changes prior to promoting them, and monitoring environments through their evolution process, engineering teams would be able to release with confidence without having to fix the same issues repeatedly. The idea is not to prevent infrastructure changes but to make sure that all changes made are intentional, validated, and consistent with the organization’s architectural requirements.

AI & Data
How to Connect Your AI Assistant to InfrOS
Harel Dil
Nov 5, 2026
·
6 min read

You can now use InfrOS straight from the AI assistant you already work in. Once it's connected, your assistant can design cloud architectures with you, using your own InfrOS account and permissions. No new tool to learn, and no copy-pasting between tabs.

Setup takes a few minutes. Here's everything you need.

What you need

You only need three things. First, an InfrOS account. Second, a supported assistant. Third, the InfrOS MCP address, which is https://api.app.infros.io/assistant/mcp

These assistants and plans work today:

  • Claude: Free, Pro, Max, Team and Enterprise
  • Claude Code: any plan that includes Claude Code
  • ChatGPT: Business, Enterprise and Edu
  • Codex: any ChatGPT plan that includes Codex
  • Cursor: any plan

We're adding more assistants. If yours isn't on the list, let us know.

Set it up in your assistant

Pick your assistant below and follow the steps. Every option ends the same way. You sign in to InfrOS and click Allow.

‍

Claude

  1. Open Customize, then Connectors.
  2. Click + Add, then Add custom connector.
  3. Name it InfrOS, paste the InfrOS address, then click Continue and Add.
  4. Sign in to InfrOS and click Allow.

On Team and Enterprise plans, an Owner adds InfrOS once in Organization settings, then Connectors. After that, each member just clicks Connect next to InfrOS.

‍

Claude Code

Run this in your terminal:

claude mcp add --transport http infros https://api.app.infros.io/assistant/mcp

Then type /mcp in Claude Code, choose infros, choose Authenticate, and click Allow in InfrOS.

‍

ChatGPT

  1. Open Settings, then Apps & Connectors, then Advanced settings, and turn on Developer mode.
  2. Add a connector named InfrOS with the InfrOS address, and choose OAuth to sign in.
  3. Sign in to InfrOS and click Allow.

Codex

Run these two commands:

codex mcp add infros --url https://api.app.infros.io/assistant/mcp
codex mcp login infros

Then click Allow in InfrOS.

‍

Cursor

Add InfrOS to ~/.cursor/mcp.json:

{
 "mcpServers": {
   "infros": {
     "url": "https://api.app.infros.io/assistant/mcp"
   }
 }
}

Then open Cursor's MCP settings, sign in to InfrOS, and click Allow.

What your assistant can do

You stay in control. When you connect, InfrOS shows you exactly what the assistant is asking to do. It can only do what you allow, and only what your InfrOS role already lets you do.

  • Read: see your Systems, specifications, landing zones and architecture proposals. Anyone can allow this.
  • Write: create Systems and versions, and edit drafts. Anyone can allow this.
  • Spend: start design runs and Terraform generation, which use your organization's credits. Only organization admins can allow this.
  • Admin: manage landing zones, standing constraints and GitHub repositories. Only organization admins can allow this.

Credits never get spent by surprise. Your assistant always tells you the price first and waits for you to say yes.

How to disconnect

Changed your mind? Open your Profile in InfrOS, go to Connected assistants, and click Revoke.

Try it now

Connect your assistant, then ask it to design an architecture for a real workload you're planning. It's the same InfrOS you know, just from inside your chat. Want a walkthrough first? Book a demo and we'll set it up with you.