Skip to main content

Use cases

Each use case names a task and links to the guide that does it. Changes arrive as pull requests: written changes that you can read before you merge them.

Put an app you built into production​

  • Ship a first site. Point Infrastream at a repository. It proposes a deployment as a pull request. Merge the pull request to put the site online. Guide: Deploy an Application.
  • Use your own domain. One PublicIngress manifest binds the domain, creates the DNS zone and requests the HTTPS certificate. Then you point the name servers of the domain at the new zone. Guide: Set Up a Custom Domain.
  • Put a login on one page. Identity-Aware Proxy asks for a sign-in before it passes a request to a route, for example /admin. The rest of the site stays public. Guide: Adopt a Repository, DNS and Sign-in.
  • Turn a site into an app. Declare a frontend, an API and a PostgreSQL database. The API gets access to the database through its accessControl block. Guide: Provision a Database.
  • Let customers sign in. An IdentityProvider manifest creates a sign-in tenant for your customers. A route rule requires it, and the backend receives a verified identity. Guide: Adopt a Repository, DNS and Sign-in.
  • Let Beck draft database changes. Describe the change in plain words. Beck drafts it as a pull request, and the database changes when you merge. Guides: Run Database Migrations and Use Beck.
  • Add a chat channel. A service that receives WhatsApp messages calls the same API and database as the website. You register the number and the webhook with Meta, not in a manifest. Guide: Manage Secrets.
  • Give a bot its own identity. A verified phone number maps to the same customer identity as the website. The bot has an identity of its own, separate from the customer. Reference: IdentityProvider.
  • Add a mobile app. The app signs in against the same customer identity and calls the same API. Reference: HttpRoute.

Grow a team​

  • Let Beck handle routine changes. Ask Beck to raise a memory limit or add an environment variable. Beck reads the live state and opens a pull request. Any engineer can review it. Guide: Use Beck.
  • Make a staging copy. Manifests describe everything, so a second environment is a second set of files. Put the copy to sleep on a schedule. Guide: Control Costs.
  • Connect projects privately. A PrivateIngress gives projects one internal address. You list the projects that may use it. The platform publishes nothing to the internet. Guide: Set Up Private Ingress.
  • Decide who can reach what. Outbound access is an allow-list in the Project manifest. Inbound access is the list of authorized projects on the private ingress. Guide: Configure Egress Rules.
  • See the whole estate. The portal shows each resource, the links between resources and the project of each resource. It stays current as changes merge. Read: Architectural Overview.

Govern an estate that already exists​

Infrastream does not scan a project to write manifests. A person describes the resources that already run, and the engine adopts what it finds. Infrastream does this work with you as a scoped task. The portal has no button for it.

  • Make data access visible. Write the storage and its access as manifests, so a grant becomes a line in a pull request. A Bucket manifest does not adopt a bucket that already exists. It creates a new bucket. Check that the plan shows an import before you approve. Guide: Create a Bucket.
  • Move an app without a rewrite. Describe the image and the service that already run in an ExternalApplication manifest. The engine finds that service and records it as managed. It does not create a second copy. Guide: Deploy an Application.
  • Migrate one project at a time. Describe each project where it runs. Other projects stay as they are. Read: Core Concepts.
  • Limit what an agent can reach. An agent signs in through the same identity system as your staff. Its accessControl block lists the databases, secrets and topics it can reach. No manifest field sets finer rules for one dataset or workload. Read: Agentic Governance.

Rules that hold in every use case​

  • Each pull request shows a monthly estimate for the fixed-cost parts it can price. The estimate is not the bill. Usage costs more on top.
  • Settings revert with the commit. Deleted data does not come back with it.
  • Apps can call only the sites that their project lists, plus Google's services and operating-system update servers.
  • Your repository branch rules decide if a review must happen before the merge. Organization admins can bypass those rules.
  • For workflows with the Infrastream MCP, read the MCP Workflows Playbook.