xAutodocs Sign in

What xAuto is, and the four steps from an empty organization to a screen with your infrastructure on it.

Getting started

xAuto is a control plane for infrastructure you already own. It does not host that infrastructure or use its own cloud identity to operate it. Every call it makes to AWS, Azure, MongoDB Atlas or any other provider runs under a connection credential you register, scoped however you choose to scope it. The encrypted credential is held in the platform's secret store and is never returned after registration.

Nothing in the app works until it knows three things: which project you are working in, which environment of it, and which connection to reach the provider through. Those three are the subject of Projects, environments and connections, and they are why most screens are locked until a project is selected.

The four steps

  1. Create a project. A project is a system you operate — one product, one platform, one team's estate. Open Organization → Projects and create one. If your organization was just created, this is the only thing you can do until it exists.

  2. Add an environment. Environments are yours to name: QA, UAT, Staging, Production, dev-eu. Production environments get extra safety — see Pipelines and approvals — and the name is what identifies one, so keep them consistent across projects if you can.

  3. Register a connection. A connection binds one provider account to the project, optionally scoped to one environment. Open Connectors, choose the provider, and supply its credential. The credential is written straight to AWS Secrets Manager and is never returned by any response afterwards — see Connections.

  4. Import your resources. Open Resources and import from the connection you just made. Importing does not create or change anything in your cloud account; it records which resources you want this platform to track, watch and cost.

Once resources are tracked, the Dashboard becomes the screen worth leaving open. From there you can manage each resource, build reusable Blueprints, automate deployments with Pipelines, and add approval gates around sensitive changes.

Picking your project and environment

The project, environment and connection switcher in the page header is the app's context. Nearly every screen reads it, so switching project or environment there changes what every screen shows — it is not a filter on one page.

The selection rides along in the URL as ?project=&env=, so a link you copy reproduces the exact screen and the context it was copied from. That is the easiest way to hand a colleague something you are looking at.