Skip to main content

Meet Beck

Beck is the AI assistant in the Infrastream portal. You describe a change in plain words. Beck returns manifests as a pull request, a diagnosis or a plan. Beck works from the real state of your estate, the manifest schema and the sample templates.

Beck is for the members of your own organization, not for your clients. Beck uses Google's Agent Development Kit (ADK) and runs on Vertex AI Agent Engine.

Current status and limits

The agentic layer is early and in active development. The agent runtime supports ADK only. Test agent deployments again in each environment before you use them in production. Governance is still in progress.

How Beck changes infrastructure​

Beck does not call cloud APIs to change your infrastructure. It uses the same Git flow as a person:

  1. Beck proposes manifests as a pull request with a plan of what will change.
  2. Your branch rules decide if a review must happen before the merge. CODEOWNERS review applies as far as those rules enforce it. A release-track approval gate applies where a stage has an approval policy. The GitHub app of the assistant and organization admins can bypass the rules. Check this setting. Do not assume it.
  3. The engine applies what you merge.

What you can ask​

  • Write configuration. "Write a DeploymentConfig for billing-service that scales 2 to 10 and injects DB_PASSWORD from Secret Manager."
  • Diagnose. "Why did the AstraPay database fail to provision?"
  • Reason about the estate. "Which applications depend on the payments database, and what breaks if I resize it?"
  • Audit and plan. "Are any VMs in staging attached to an insecure subnet?"

Next​