Skip to main content
A guided path from workspace setup through cluster creation, package selection, and a running installation checkpoint.
This guide takes you from software source to a customer-ready setup on Akua. By the end, you will have a Package version, a Product that wraps that specific version, and an Offer or direct install path customers can use. Installations choose the cluster target when they are created. No Kubernetes or DevOps experience is required. Akua manages the underlying infrastructure so you can focus on what you ship.

Start the interactive quickstart

The guided onboarding in the dashboard is the fastest path to your first Product.

​
Prerequisites

  • An Akua account (sign up at akua.dev).
  • A Package for your software: start from an authored package.k or a supported source such as a Helm chart, GitHub repository, or container image.
  • A Stripe account, only if you plan to charge for installs. See Payments for the connected account setup.

​
Which path are you on?

Choose the path that matches what you are trying to do.
  • Install first: start with Clusters if you want to prepare compute before you package or sell anything.
  • Set up a Product: use this quickstart to create or select a Package, wrap a concrete Package version as a Product, and prepare an Offer or direct install path.
  • Redeem an Offer as a customer: follow the customer flow in Offers and Installations after someone has already published the Product.
This quickstart is the second path: it helps you turn software source into a Product setup that can be offered to customers or used to create installations. It does not replace the customer redemption flow.

​
What the interactive quickstart does

The guided quickstart runs inside the dashboard and walks you through Product setup end to end. It helps you pick a source or select an existing Package, choose a Package version, wrap that version as a Product, and generate a shareable Offer or direct install path. Each step is checked off as you complete it, so you always know what is left before your software is ready for customers. If you prefer to work through the flow yourself, the steps below mirror what the guided quickstart automates.

​
What you’ll do

Create a Package

Create or select a Package definition from your software source. Akua turns it into a reusable, versioned install contract.

Wrap it as a Product

Choose the concrete Package version customers should install, then add product metadata, default Inputs, and visibility.

Prepare an install target

Create or select a managed or imported . The installation targets this cluster when someone installs the Product.

Choose how customers get it

Create an Offer link for direct distribution, or list the Product on your marketplace if commerce is enabled for your workspace.

Go live

Customers open your Offer link, configure the Package Inputs, and complete the install through the guided customer flow.
You can build Packages and share free installs without Stripe. To accept payment when commerce is enabled for your workspace, connect your own Stripe account from Settings → Stripe. Akua uses hosted Stripe Checkout and never holds your funds.

​
What’s next

After the quickstart, your Product has a Package version and a customer entry point. Each installation chooses the cluster target when it is created.

Offers

Configure private offer links and the customer purchase flow.

Payments

Connect Stripe when commerce is enabled for your workspace.

Add more products

Wrap more Packages into customer-facing software offerings.

Import an existing cluster

Connect Kubernetes infrastructure you already operate instead of creating a new cluster.

Installations

Learn how installations are rendered, configured, and updated once a Product is ready.

Explore platform capabilities

See how Compute, Packaging, Delivery, Networking, Commerce, Agents, and Platform fit together.

​
Background concepts

A cluster is a group of machines working together under Kubernetes. Workers are the compute nodes where your products actually run. Akua’s managed clusters handle the Kubernetes control plane for you: you add your own worker machines and Akua takes care of the rest.
Regions let you organize your infrastructure by geography. Choosing the right region improves performance for your customers and can help meet data residency requirements.
  • Regions are named by location: for example, fsn1 for Falkenstein, Germany on Hetzner Cloud.
  • Deploying in multiple regions provides redundancy and lower latency for global customers.
Akua Packages are the versioned install contract that Products, Offers, and direct installs reuse. A Package can be authored directly with package.k or generated from supported sources such as Helm charts, GitHub repositories, and container images.
Akua integrates with to handle customer payments. You connect your own Stripe account through the dashboard.
  • You do not need a Stripe account to try Akua or test installs.
  • Connect Stripe from Settings → Stripe when you are ready to accept purchases.
  • Paid checkout is enabled for workspaces where commerce is enabled.
  • Akua uses hosted Stripe Checkout and never holds your funds.

​
Troubleshooting

  • Confirm the machine has outbound internet access.
  • Verify you copied the full join command without truncation.
  • Run the command as root (with sudo).
  • Wait 2–3 minutes for the connection to establish, then refresh the dashboard.
You can connect it to Akua instead of creating a new one. See the cluster import guide →.

Concepts

Understand packages, sources, products, and installations.

Packages

Learn how Package versions power Products, Offers, and direct installs.

Clusters

Managed and imported Kubernetes infrastructure.

Offers

Create customer distribution paths for a Product.