One implementation. One price. A working platform in weeks.
Vertro standardizes Application onboarding, Google Cloud infrastructure, and secure delivery on GKE — fixed cost, no per-seat billing, delivered inside your own environment.
Built on the tools already in your stack
A complete, standardized Application delivery path on GKE — from your first Application to expanded delivery across more teams and Environments, all part of the same engagement.
Platform foundation
- Vertro Portal and Orchestrator setup
- Google Cloud infrastructure provisioning workflow
- GKE namespaces, quotas, and baseline policies
- Workload Identity Federation for Applications and CI/CD
Delivery & GitOps
- Golden Path Application templates
- Standard CI/CD with private self-hosted runners
- GitOps foundation with Config Sync and Argo CD
- Helm-based delivery and promotion workflows
Security & governance
- Core platform security and governance controls
- Code, infrastructure, and container image scanning
- Controls to help ensure only approved images ship
- Platform policies and guardrails
Onboarding & advisory
- Guided onboarding of your first Applications
- Onboarding for additional Applications and Environments
- Additional Application onboarding templates
- Platform architecture and optimization advisory
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 is a focused implementation path to 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 fees
Your costs do not increase simply because more teams adopt the reusable onboarding and delivery patterns.
Your team owns the platform
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, depending on your existing foundations and integration complexity.
Week 1 — Discovery
Access setup, architecture alignment, baseline configuration, and Google Cloud and GitHub integration planning.
→ Confirmed scope and target architecture
Week 2 — Build
Platform setup, Application onboarding workflow, infrastructure provisioning, Workload Identity Federation, CI/CD, and GitOps configuration.
→ First working, repeatable delivery path
Week 3 — Harden & hand off
Additional security controls, policies, promotion workflows, guided onboarding, documentation, and handoff.
→ Operational platform ready for internal ownership
Optional ongoing platform support
Onboarding help, Golden Path improvements, workflow updates, policy refinement, troubleshooting, and architecture review.
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.
Is Vertro a SaaS product?
No. Vertro is delivered as a productized platform implementation inside your Google Cloud and GitHub environment, not a per-seat SaaS portal.
Is the implementation price monthly?
No. The listed price is a one-time implementation price. Optional ongoing platform support is priced separately.
How long does implementation take?
Most implementations are delivered within 2–3 weeks, depending on access, existing foundations, security requirements, and approval timelines.
Do we own the platform?
Yes. Vertro is implemented using your repositories, infrastructure, and security controls. Your team owns and operates the resulting platform.
How many Environments are included?
Environment scope depends on your target architecture and is confirmed during scoping, including onboarding additional Environments as part of the same implementation.
How many Applications are included?
The implementation includes guided onboarding of your first Applications, with onboarding for additional Applications available as part of the same engagement.
Are Applications and Environments usage limits?
No. They define the implementation scope. Vertro does not charge per Application, Environment, or platform user.
What security capabilities can Vertro include?
Code, infrastructure, and container image scanning; Workload Identity Federation; policy enforcement; and controls to help ensure only approved images reach production.
Who is Vertro for?
Engineering teams on Google Cloud and GKE that want standardized, secure delivery without building a large IDP program from scratch.
Can final pricing change?
Yes. Final pricing depends on your existing Google Cloud organization, GKE and networking foundations, GitHub setup, and security requirements.
Can we start with a smaller implementation?
Yes. The engagement can start with your first standardized delivery path, then expand to more Applications, Environments, and teams.
See it running in your own Google Cloud environment
One fixed-cost implementation. No per-seat pricing. Delivered in 2–3 weeks.