MANSSINO / Request a machine
Tell us what you are running.
MANSSINO is rolling out through a waitlist, and we read every request. The more concrete you are about the workload, the faster we can match a shape to it and send you a key that is useful on the first command.
What to include
- The workload: agents, training, crawling, pipelines, or something we have not seen yet
- Roughly how many machines you expect to run at once
- Anything unusual: a GPU, a large dataset, a region, a security requirement
Request access
waitlist openRequest ready to send.
Your mail client should have opened with the details filled in. Send that message and it reaches our team directly. If nothing opened, write to hello@manssino.co and paste the same details.
We reply to every request, usually within two business days.
01 Before you ask
Common questions about access.
How long is the waitlist?
It moves by workload fit rather than by position. Teams whose work maps cleanly onto persistent machines, which usually means long, stateful, privileged jobs, go first because they tell us the most about the platform while it is still young.
What arrives with access?
An API key, a CLI profile, and a machine already created in the shape we agreed on. The quickstart covers the first four commands, and the whole surface is small enough to read in one sitting.
Can we talk to an engineer first?
Yes. Say so in the message and we will set up a call rather than sending a deck. Architecture and security questions are answered by the people who built the thing.
We have a security review process. Will that slow this down?
It does not have to. Send your questionnaire with the request and we will work through it in parallel with provisioning. The security model answers most of it already, including the shared responsibility line.
How does pricing work during the rollout?
Billing is for active compute time, with nothing charged while a machine sleeps. We will give you the specific rate for your shape and region with your access invitation, so there is nothing to discover on the first invoice.
While you wait
Read how the machine actually works.
The platform page covers the architecture, the lifecycle, and the resume path. The developer page covers every command and endpoint there is.
- The architecture, from the hypervisor up to your shell.
- Every lifecycle state and exactly what each one costs.
- The full command and endpoint surface, in one sitting.
- Where a persistent machine fits, and where it does not.