Infrastructure Designer

The Infrastructure Designer is a conversational way to add the AWS building blocks your app depends on, things like queues, buckets, and other managed services, without leaving Ownkube. You describe what you need in plain language and the Designer proposes the components, shows you exactly what it will create, and provisions them into your own AWS account once you confirm.

How it works

Connect an AWS account

The Designer provisions into your own account, so a connected and verified AWS account is required. If none is connected, the Designer prompts you to finish AWS onboarding first.
Start a design session

Open a session and describe what your app needs, for example “my worker needs a queue and a bucket for uploads.” Each session is a saved conversation you can return to.
Review the proposal

The Designer turns your request into a concrete set of components and shows them on a canvas before anything is created. Nothing is provisioned until you approve.
Provision into a deployment

On confirmation, the components are created in your AWS account and wired to the deployment you’re working with, so your app can use them straight away.

What you get

Plain-language input. Describe outcomes, not configuration. The Designer maps them to concrete AWS components.
Confirm before provisioning. You always see the proposed components first. Provisioning only happens after you approve.
Scoped to your organization. Sessions and the components they create belong to your organization and land in your own AWS account.
Deployment-aware. Components can be attached to a specific deployment so your app picks them up.

Early-access limits

Not generally available. Access is gated and may be limited to specific environments while in early access.
AWS only. The Designer provisions into AWS accounts you’ve connected.
Subject to change. Component coverage, the proposal canvas, and provisioning behavior are still evolving.