Skip to content
  1. Docs
  2. Integrations
  3. Private cloud and SSO
Integrations

Private cloud and SSO

Companies that must keep applications inside their own cloud account can run Autoflowly apps on their own Kubernetes cluster in AWS, Azure or Google Cloud, while still building and operating them from Autoflowly. Staff sign in with the company's identity provider.

Bring your own cloud#

The model is a runner: a small component you install in your cluster that opens an outbound-only connection to Autoflowly. Autoflowly never needs inbound access to your network, no credentials to your cloud, and no public endpoint on your side.

  1. Register a cluster#

    In the web app, add a cluster and give it a name and region. You receive an enrollment token that is valid once.

  2. Install the runner#

    Apply the install command or setup script shown for your cluster. Terraform modules for AWS, Azure and Google Cloud create the cluster and install the runner in one step if you prefer. The runner image is signed and ships with a software bill of materials.

  3. Build as usual#

    Choose the cluster when you create an app, or move an existing app. Builds, chat edits, the AI team and approvals work exactly as they do on Autoflowly's cloud; only the place where the app runs changes.

What stays on your side: the app containers, their databases and files, and the traffic between your users and your apps. What goes through Autoflowly: the build instructions, the AI calls the builder and agents make, and the operational metadata the dashboard shows. The cluster's audit log can be forwarded to your SIEM through a signed webhook.

Data residency#

App databases can be placed in the EU on Autoflowly's cloud (Frankfurt or Berlin) by request, independent of the private-cloud option. AI inference for building and agents currently runs with Autoflowly's model providers; an EU-region inference profile is in development and not yet available.

Single sign-on#

Autoflowly supports OpenID Connect sign-in for teams, so staff use the company's identity provider instead of personal Google or GitHub accounts. Groups from the provider can map to roles. Apps built for your company can use the same broker so your staff sign in to each app with the company identity.

Not yet available#

  • An organisation-wide view across many owners' apps, central policy floors and SCIM provisioning are in development.
  • Customer-supplied AI keys or EU-only inference are in development.

For current status, contractual terms and a security review, contact us with the subject Enterprise.

Last reviewed 21 October 2026Something wrong or missing? Tell us