Deploy an Internal Developer Platform for Google Cloud in weeks, not months.
Fixed-cost implementation for engineering teams that want to standardize Application onboarding, Google Cloud infrastructure provisioning, and secure delivery without building an Internal Developer Platform from scratch.
Implementation plans
Vertro is delivered as a productized implementation inside your Google Cloud and GitHub environment. Your team receives a working platform foundation that it owns, operates, and extends over time.
First standardized Application delivery path
For teams that need a repeatable foundation for onboarding and securely delivering Applications on GKE.
- Vertro Portal and Orchestrator setup
- Application onboarding workflow
- Google Cloud infrastructure provisioning workflow
- Golden Path Application templates
- Standard CI/CD workflow foundation
- Private self-hosted GitHub Actions runner foundation
- GKE namespaces, quotas, and baseline policies
- Workload Identity Federation for Applications and CI/CD
- GitOps foundation with Config Sync and Argo CD
- Helm-based Application delivery patterns
- Core platform security and governance controls
- Guided onboarding of two initial Applications to establish and validate the reusable delivery path
Scale secure Application delivery across more teams
For teams expanding standardized onboarding, secure delivery, approvals, and governance across additional Applications and Environments on Google Cloud.
- Everything in Platform Foundation
- Additional Golden Paths and Workload Types
- Onboarding for additional Applications and Environments
- Expanded approval and promotion workflows
- Code, infrastructure, and container image scanning
- Controls to help ensure only approved images reach production
- Additional platform policies and governance controls
- Additional Application onboarding templates
- Platform architecture, optimization, and implementation advisory
Optional ongoing support
Some teams operate Vertro independently after implementation. Others prefer ongoing support as they onboard additional Applications, refine platform standards, and expand delivery controls.
Platform evolution and implementation support
Optional support for teams that want continued platform guidance and implementation assistance after the initial engagement.
- Support onboarding additional Applications
- Improve Golden Paths and onboarding templates
- Update platform workflows and integrations
- Refine policies, guardrails, and governance controls
- Troubleshoot CI/CD and platform workflows
- Review architecture and platform evolution decisions
Support is based on an agreed monthly allocation and does not include 24/7 operations, incident response, or full platform management unless separately scoped.
Why this pricing model is different
Many Internal Developer Platform initiatives begin as large software purchases, open-ended consulting engagements, or multi-month transformation programs. Vertro provides a focused implementation path for teams that want a working, customer-owned platform foundation sooner.
No per-seat pricing
Pricing is not tied to the number of developers, Applications, Environments, or platform users.
No usage-based Vertro fees
Your costs do not increase simply because more teams adopt the reusable onboarding and delivery patterns.
Your team owns the platform
Vertro is implemented in your Google Cloud and GitHub environment using your repositories, security controls, and operating model.
Typical implementation timeline
Most implementations are delivered within 2–3 weeks. The final timeline depends on your existing Google Cloud organization, GKE and networking foundations, GitHub setup, security requirements, and integration complexity.
| Phase | Typical work | Outcome |
|---|---|---|
| Week 1 | Discovery, access setup, architecture alignment, baseline configuration, and Google Cloud and GitHub integration planning | Confirmed implementation scope, target architecture, and platform baseline |
| Week 2 | Vertro platform setup, Application onboarding workflow, infrastructure provisioning, Workload Identity Federation, CI/CD, and GitOps configuration | First working and repeatable Application onboarding and delivery path |
| Week 3 | Additional security controls, policies, promotion workflows, guided Application onboarding, documentation, and handoff | Operational platform foundation ready for continued adoption and internal ownership |
Frequently asked questions
Does Vertro provision Google Cloud resources?
Yes. Vertro provides standardized workflows for provisioning Google Cloud resources such as projects, IAM, Cloud SQL, Secret Manager, Cloud Storage, Artifact Registry, and other Application infrastructure. It can also generate Application repositories, GKE namespaces, Workload Identity Federation configuration, CI/CD workflows, and platform guardrails.
Is Vertro a SaaS product?
No. Vertro is delivered as a productized platform implementation inside your Google Cloud and GitHub environment. It is not sold as a per-seat SaaS portal.
Are the Platform Foundation and Platform Growth prices monthly?
No. The listed prices are one-time implementation prices. Optional ongoing platform support is priced separately.
How long does implementation take?
Most implementations are delivered within 2–3 weeks. The timeline depends on access, your existing Google Cloud and GKE foundations, networking, security requirements, integrations, and approval timelines.
Do we own the platform?
Yes. Vertro is implemented in your Google Cloud and GitHub environment using your repositories, infrastructure, security controls, and operating model. Your team owns and operates the resulting platform foundation.
How many Environments are included in the initial implementation?
The included Environment scope depends on the selected plan and your target architecture. Platform Foundation establishes the initial delivery path, while Platform Growth can include onboarding additional Environments and promotion workflows.
How many Applications are included in the initial implementation?
Platform Foundation includes guided onboarding of two initial Applications to establish and validate the reusable onboarding and delivery pattern.
Are the included Applications and Environments usage limits?
No. They define the guided onboarding and implementation scope included in the engagement. Vertro does not charge per Application, per Environment, or per platform user. Your team can continue reusing the established platform patterns after implementation.
What security capabilities can Vertro include?
Vertro can include code, infrastructure, dependency, and container image scanning; Workload Identity Federation; policy enforcement; approval and promotion workflows; and controls designed to help ensure that only approved container images reach production. The exact controls depend on the selected plan and implementation scope.
Who is Vertro for?
Vertro is designed for engineering teams using or adopting Google Cloud and GKE that want to reduce manual onboarding, standardize secure Application delivery, and establish reusable platform guardrails without building a large Internal Developer Platform program from scratch.
What is Vertro not?
Vertro is not a generic developer portal, a cloud-agnostic platform toolkit, or a per-seat SaaS product. It is an opinionated Google Cloud and GKE platform implementation designed to provide a working, customer-owned platform foundation quickly.
Can final pricing change?
Yes. Final pricing depends on your existing Google Cloud organization, GKE and networking foundations, GitHub setup, Environment model, security requirements, selected platform capabilities, and integration complexity.
Can we start with a smaller implementation?
Yes. Platform Foundation is designed for teams that want to establish and validate the first standardized Application onboarding and delivery path before expanding across more Applications, Environments, and teams.