Skip to content

Getting started

What ALYNREX gives you, and the shortest path from an account to a running workload.

Getting an account

There is no public sign-up on this platform today. An operator creates your account, or you are invited to an existing project. Once your account is active you always have a personal project to work in, even before anyone shares one with you.

Platform setting, checked 2026-09-14

ALYNREX runs container workloads on managed Kubernetes in Batam, Indonesia. You do not manage the cluster, the control plane, or the networking. You get a project, one or more namespaces bound to it, and the ability to deploy into them from the console.

The shape of the platform

Three things, and everything else hangs off them.

Projects own everything. Members, roles, the namespaces the project is allowed to deploy into, and the spend. If you cannot see something in the console, the usual reason is that it belongs to a project you are not a member of.

Namespaces are where workloads actually run. A namespace is bound to exactly one project on exactly one cluster, and that binding is what gives your project somewhere to put things.

Workloads are what you deploy — an image, a number of replicas, a port, and the resources it is allowed to use. Most workloads are created from a template, which fixes those values so that deploying is a choice between known-good shapes rather than a form with thirty fields.

Your first deployment

  1. Sign in to the console and pick a project. If you have never used one before, your personal project is already there.
  2. Check the project has a namespace. Under the project, the Namespaces view lists what it owns. If it is empty, a project admin has to bind one — see Projects and roles.
  3. Deploy from the catalog. Choose a template, give the workload a name, and pick the namespace. The template decides the image, replicas, port and resource limits.
  4. Watch it come up. The workload’s page shows pod status and logs. A workload that cannot pull its image or cannot fit in the namespace’s quota says so here rather than failing silently.

What you can do next

  • Give a colleague access — Projects and roles covers what each role can do, and the two that catch people out.
  • Understand what you can change after deploy, and what is deliberately fixed — Workloads.

Getting help

The console’s audit log records every change made to your project, including who made it and whether it succeeded. It is the fastest way to answer “what happened to this workload” before asking anyone.

If you need something the console will not let you do, that is often a role boundary rather than a missing feature. Projects and roles explains which.