Google Cloud Vertex AI
Google Cloud Vertex AI is Google's unified machine learning platform: hosted Gemini and partner model APIs, custom model training, orchestration pipelines, notebooks, a model registry, feature serving, and monitoring on one surface. Google is renaming it the Gemini Enterprise Agent Platform; the Vertex AI name still dominates the SDK and practitioner tooling.
itArtificial intelligence and machine learning | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic — Google Cloud Vertex AI
Vertex AI, honestly, is Google renting you its machine learning plumbing: the models (including Gemini, the one from the adverts), the training compute, the serving machinery, and a small museum of MLOps services, all under one bill. Google now prefers to call it the Gemini Enterprise Agent Platform. It renamed the platform while most of the world was still learning the old name, which tells you something about who this relationship serves.
Before it existed, running ML on Google Cloud meant stitching together separate services: one for training, one for hosting, notebooks somewhere else entirely. Vertex AI's whole pitch is that these are one platform now. The pitch mostly holds.
Three ideas carry the platform.
The two faces. One face is the modern one: call Gemini and partner models through an API, pay per token, tune them if prompting disappoints. The other face is classic ML: submit your own training container, let Google run it serverless, register the result. Same bill, very different workflows. Knowing which face your problem belongs to is half the navigation.
The endpoint. Serving runs through a resource called an Endpoint: deploy a model there and it can take predictions. Multiple models can share one endpoint with a traffic split, which is how careful teams roll out new versions. This is also where the platform's most expensive surprise lives, so it gets its own paragraph.
Deployed means paying. A model that is deployed to an endpoint bills node-hours continuously, whether ten million requests arrive or zero. The minimum replica count is one, and there is no scale-to-zero in the standard path. Every idle test endpoint you have forgotten about is a subscription you did not mean to start. The single most valuable Vertex habit is undeploying things the moment they stop being interesting. The pricing page states it plainly: you pay for each deployed model even with no prediction, and you must undeploy to stop.
What will surprise you? The quota system, in one word: shared. Gemini capacity follows a Dynamic Shared Quota, a phrase meaning there are no fixed limits to check, so throttling can arrive while the dashboard peacefully shows headroom. Guaranteed throughput exists and costs extra. Teams discover this during their first 429 storm, usually at the worst possible hour.
A gentler surprise: the bill can show line items for services you never knowingly enabled, because AutoML jobs quietly incur pipeline-run fees and metadata storage. Read the pricing fine print before the first experiment, not after the first invoice.
Where next? The Cheatsheet compresses the two faces into tables, the Reference tab starts with Google's own documentation, and the Timeline tab explains why your bookmarks say Vertex AI while the console says something else. The quiz is kind: it will not ask you to name the rebrand from memory. It will ask what an idle endpoint costs, which is the question that actually keeps money in your account.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://cloud.google.com/vertex-ai/docs/start/introduction-unified-platform
Supports
- Vertex AI as unified platform for build, train, manage
- Serverless training benefits; framework support (PyTorch, TensorFlow, scikit-learn, XGBoost)
- https://cloud.google.com/vertex-ai/generative-ai/docs/overview
Supports
- Model Garden contents: Google models, partner models, open models
- Tuning methods (supervised, preference, RL, LoRA/QLoRA)
- Evaluation options (AutoSxS, rubric, computation-based)
- Consumption options (Provisioned Throughput, Standard, Priority, Flex, Batch)
- https://cloud.google.com/vertex-ai/generative-ai/docs/tuning
Supports
- Prompt first, tune with labeled data (about 100+ examples) guidance
- https://cloud.google.com/vertex-ai/docs/pipelines/introduction
Supports
- Pipelines as DAGs of containerized components (Kubeflow/TFX SDKs)
- Compilation, scheduling, metadata and lineage
- https://cloud.google.com/vertex-ai/docs/workbench/introduction
Supports
- Workbench as managed JupyterLab with deep learning preinstalls
- Executor for scheduled runs; limitations
- https://cloud.google.com/vertex-ai/docs/general/deployment
Supports
- Deploy models to endpoints; fixed deployment settings
- Multiple models per endpoint with traffic splitting
- Rolling deployments; autoscaling on concurrent requests
- Endpoint URL pattern
- https://cloud.google.com/vertex-ai/docs/predictions/autoscaling
Supports
- minimum replica count at least 1; no scale-to-zero for custom deployments
- https://cloud.google.com/vertex-ai/pricing
Supports
- Per machine-hour billing in 30-second increments; accelerators separate
- You pay for each model deployed to an endpoint, even if no prediction is made
- Pipelines per-run fee; each AutoML job counts as one managed pipeline run
- ML Metadata storage billed per GiB-month
- Feature Store pricing structure; registry free
- https://cloud.google.com/vertex-ai/docs/featurestore/latest/overview
Supports
- Feature Store as managed service over BigQuery sources; Bigtable online serving
- https://cloud.google.com/vertex-ai/docs/model-registry/introduction
Supports
- Model Registry as central repository; aliases; BigQuery ML registration
- https://cloud.google.com/gemini-enterprise-agent-platform/machine-learning/start/introduction-mlops
Supports
- MLOps surface summary: pipelines, metadata, experiments, registry, feature store, monitoring
- Model Monitoring detects training-serving skew and inference drift
- https://cloud.google.com/vertex-ai/docs/quotas
Supports
- Quotas per project per region, shared across applications
- Separate rate quotas per operation class
- Model Registry max model size 1 TB
- https://cloud.google.com/vertex-ai/generative-ai/docs/quotas
Supports
- Generative model quota structure; DSQ framing for Gemini models
- https://cloud.google.com/gemini-enterprise-agent-platform/vertex-ai-name-changes
Supports
- Official renaming table (Vertex AI to Gemini Enterprise Agent Platform)
- https://cloud.google.com/blog/products/ai-machine-learning/introducing-gemini-enterprise-agent-platform
Supports
- Agent Platform as the evolution of Vertex AI; all Vertex services delivered through Agent Platform
- https://cloud.google.com/gemini-enterprise-agent-platform/notebooks/workbench/instances/idle-shutdown
Supports
- Idle shutdown keyed on kernel activity, not CPU
- Disk storage charges continue while shut down
- https://cloud.google.com/sdk/gcloud/reference/ai/
Supports
- gcloud ai command groups and subcommands
- https://pypi.org/project/google-cloud-aiplatform/
Supports
- google-cloud-aiplatform package identity; formerly-known-as note
- Deprecation of generative modules in favor of google-genai
- https://cloud.google.com/blog/products/gcp/introducing-google-cloud-machine-learning-engine
Supports
- Cloud Machine Learning Engine as managed TensorFlow training/prediction predecessor
- https://cloud.google.com/blog/topics/inside-google-cloud/announcing-vertex-ai-our-new-unified-ml-platform
Supports
- Vertex AI announced as unified ML platform at Google I/O 2021
- https://cloud.google.com/blog/products/ai-machine-learning/vertex-ai-pipelines-now-ga-serverless-orchestration-for-mlops
Supports
- Pipelines general availability with serverless orchestration
- https://cloud.google.com/blog/products/ai-machine-learning/generative-ai-support-on-vertex-ai
Supports
- Generative AI support on Vertex AI announcement (Model Garden, PaLM 2)
- https://blog.google/technology/ai/google-gemini-ai/
Supports
- Gemini launch with Vertex AI as developer platform, December 2023
- http://web.archive.org/web/20210615174333/https://cloud.google.com/vertex-ai/docs
Supports
- Vertex AI documentation live under the name by June 2021
- https://news.ycombinator.com/item?id=43885003
Supports
- Field Notes: Google engineer on the record, "There are no quotas in DSQ"; Provisioned Throughput as the guarantee
- https://news.ycombinator.com/item?id=43885112
Supports
- Field Notes: Provisioned Throughput entry tier too high for small teams
- https://news.ycombinator.com/item?id=43885167
Supports
- Field Notes: region round-robining retry loops; SDK read timeouts not configurable
- https://news.ycombinator.com/item?id=48053258
Supports
- Field Notes: EU residency rules out global models; wrapper round-robining across projects
- https://fuzzylabs.ai/blog/vertex-ai-the-hype/
Supports
- Field Notes: monitoring produced no alerts; no native drift-triggered retraining
- https://github.com/josephmisiti/awesome-machine-learning
Supports
- Discovery source for MLflow and Weights & Biases entries in Awesome Links
- https://github.com/steven2358/awesome-generative-ai
Supports
- Discovery source for ecosystem entries in Awesome Links and Landscape
