Your compute fleet,
your cloud.
Turn the machines you already own into a private cloud you run and own — no SaaS control plane, no outside dependency.
What Amini Cloud is
Compute you run and own — your hardware becomes your private cloud
Amini Cloud is compute you run and own — no SaaS control plane, no outside dependency. Drop it on one machine to start, and the hardware you already hold becomes a private cloud: compute is Amini Cloud, connectivity is ULAP One, all on machines you keep. Built in Kenya for operators who would rather own their infrastructure than rent it. Today it runs as a self-hosted private cloud; the sovereign, chain-coordinated fleet across many machines is the direction we are building toward.
What you get
Everything a tenant reaches for
Compute you control
SSH into a long-lived box, run notebooks on GPU, or serve a model — on your own hardware.
A private network per tenant
One Tailscale-compatible tailnet per org. Nothing in one tenant can see or reach another.
Typed storage and data plane
Object, block, tabular, tensor, stream, archive, multimodal — datasets versioned with lineage.
GPU and mixed hardware
From a Raspberry Pi to a DGX Spark to a gaming PC. Placement is aware of what each host can do.
Public HTTPS endpoints
Expose work at a stable hostname with automatic TLS, custom domains, and load-balancing.
Deny-by-default access
Fine-grained roles, GPU-hour budgets, and an audit trail. Cross-tenant reach is always explicit.
0.1.0 · single host
Quickstart
One host, dev posture, up in about five minutes once images cache.
# Clone the repo and bring up the full stack in one command
git clone https://github.com/ggichuru/amini.git && cd amini
make quickstart # doctor + up + demo-tenant; 10 pre-flight checks
# Open the dashboard
open http://localhost:5173How it works
Your machines, scheduled into one private cloud
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; a host is reached over a hole-punch, not a VPN
Add a host and it registers itself on-chain — gaslessly — publishing its libp2p identity, not a database IP. The control plane resolves that host from the chain and dials it directly, punching through NAT (proven: direct QUIC through Starlink carrier-grade NAT, 324 ms), and falls back to a blind relay only if the punch can’t land. No VPN, no inbound port, no gas to join — a machine behind CGNAT is a first-class host. This sovereign transport is the path we are moving to; the legacy VPN data path stays as the fallback while it is retired. How it works →