Compute on machines
their owners keep.
Amini Cloud is a decentralized compute and connectivity cloud built on AminiChain. An owner contributes a host; it registers itself on chain as a single oracle, signed with a key that never leaves the machine. You deploy slices onto those hosts and pick, per slice, where they may run.
Here to use this instance? See how to get an account. Want to run your own? Read the operator guide.
What Amini Cloud is
A cloud assembled out of hosts, with the chain as the authority
A host is a machine somebody contributed. It holds its own key and is its own on-chain oracle, so no central service can forge it or hand its identity to another machine. Identity, placement and settlement resolve against the chain, not against a vendor's database. Compute is Amini Cloud; connectivity is ULAP One. Built in Kenya, for operators who would rather own infrastructure than rent it. This is beta. Hosts register and are dialled over the chain today; the older VPN data path still ships as a fallback.
What you get
What a tenant reaches for
Compute you can reach
SSH into a long-lived box, open a notebook on a GPU, serve a model. Mark the work public and it comes up on a stable hostname with automatic TLS.
A private network per tenant
Each org gets its own overlay. A slice in one tenant is not denied a route to another tenant. It does not have one.
Residency chosen per slice
You name the countries a slice may run in when you create it, not once for the whole fleet. Placement rejects every host outside them.
Mixed hardware, GPU-aware placement
A Raspberry Pi and a DGX Spark can sit in the same fleet. The scheduler reads what a host can do before it puts anything there.
Datasets with versions and lineage
A dataset version records where its bytes came from. Turn anchoring on and the version hash goes on chain, so you can prove later what a run read.
Deny by default
Nothing reaches a slice for being nearby. The overlay, the host firewall and the container all say no first, and quotas cap what a tenant can hold.
Getting in
How accounts work on this instance
Amini Cloud is software that an operator runs on machines they control. There is no central Amini account. The operator of this instance decides who gets in, and nobody else can add you.
You have an invite link
Open it. It names the organisation that invited you and your role, and it carries you through creating an account. An organisation only admits people it has invited.
Ask the operator
This instance did not say how it gives out accounts. Ask whoever sent you this address, or open your invite link if you have one.
Want to run your own instance instead? The quickstart below is for you.
0.1.0 · single host
Quickstart
One host, dev posture. Clone it, run one target, open the dashboard. Access to the source is licensed: the clone needs a GitHub account that has been granted access to aminitech/amini-cloud, and fails with an authentication error otherwise.
# Clone the repo and bring up the full stack in one command
git clone git@github.com:aminitech/amini-cloud.git && cd amini-cloud
make quickstart # doctor + up + demo-tenant
# Open the dashboard
open http://localhost:5173How it works
How a slice finds a host
Watch a job move through the loop: in, scheduled, run, returned.
job in → scheduled → runs → result
How hosts connect · no VPN
The chain is the directory, and the host is dialled directly
Add a host and it publishes its libp2p identity on chain, not an IP in somebody's database. The control plane resolves that identity and dials the host directly, punching through NAT; when the punch cannot land, a blind relay carries the bytes. The platform funds the registration fee, so a machine behind carrier-grade NAT joins for nothing and is still a first-class host. The legacy VPN data path remains the fallback while it is retired. How it works →