Skip to main content
Version: 0.2 (next)

Hosted environments

darkshift runs hosted Infrared environments, SaaS control planes that darkshift operates. In one you get an org of your own: your Products, access groups, AgentRoles, model key and settings, kept apart from every other org. There is nothing to install and nothing to upgrade: darkshift upgrades the control plane the way Infrared delivers any Product, as a deployment watched by its release guard and rolled back if it fails.

Join the private beta​

The hosted environments are in private beta, with no billing until November 30, 2026. We accept teams into them after a conversation about what your architecture needs, so that we can place you in an environment that fits and tell you plainly if an install of your own would suit you better. Book a call or write to [email protected]. It helps to come with:

  • Where your code lives: GitHub organizations, or none yet (your org can start on Infrared's own Gitea).
  • Where your Products should run: on the hosted environment's own cluster, or in your own Google Cloud project or AWS account, and in which regions.
  • What you deploy: the kinds of services, their languages, databases and other dependencies, and any domains of your own.
  • Your constraints: data residency, compliance, network access to private systems, and anything that must not leave your cloud.
  • Your team: who will use Infrared, and the GitHub logins of the people who will set it up. They become its org admins.
  • Your agents' model provider: the Anthropic account your org's agent runs will spend on.

When we open your org, we send you its address.

Set it up​

  1. Sign in. Open your environment's address and choose Sign in with GitHub. Only logins on one of your org's access groups get in. See Sign in with GitHub.
  2. Your repos. Your org starts on Infrared's own Gitea, ready for Products, with nothing to connect. To keep your repos on GitHub instead, or beside Gitea, connect a GitHub organization you administer in Settings → GitHub. A GitHub organization belongs to one Infrared org. See Organizations.
  3. Set your model key in Settings → Model provider, so agents can build Changes. Runs spend on your Anthropic account, and each run shows what it cost.
  4. Add your team. In Workforce → Access groups, add your team's GitHub logins, each group with its role. See Access groups and access.
  5. Create a Product from a repo, a template or a zip, and ask for your first Change. See Products and Your first Change.

Where your Products run​

By default, your Products' environments run on the hosted environment's own cluster, at addresses darkshift gives them, or on your own domains.

To run them in your own cloud instead, add your Google Cloud project or AWS account as one of your org's cloud accounts. Once darkshift allows your org clusters of its own, your org admins build a GKE or EKS workload cluster there from a cluster template, or register a cluster you already have, on Clusters. The cluster is your org's alone, and its cloud bill is yours. Ask us to allow it when we open your org.

Hosted or your own install​

A hosted environment and an install of your own on GKE or EKS run the same Infrared. What an install of your own adds is the management cluster itself: you hold the platform admin role, you decide which orgs exist and which may have clusters, and you choose when to upgrade.