One server. One install command.
isobata ships as a signed release of Docker images that runs on a single Linux server in your cloud (VPC) or data centre. During the pilot we install it with you.
What you need
| Minimum | |
|---|---|
| Server | Linux x86_64, 8 vCPU, 32 GB RAM, 150 GB disk |
| GPU | One NVIDIA GPU with 24 GB of memory (for example an L4), with its driver and the NVIDIA Container Toolkit |
| Software | Docker Engine 27 or later with Compose, and the cosign signature tool |
| Network in | Port 443 from your team's network (and 80 for a Let's Encrypt certificate) |
| Network out | Your code host, the Figma API if you use it, our image registry, and the model publishers for the first download |
| Access to your sources | A read-only token for GitLab or GitHub; a Figma personal access token, optional |
Sizes are indicative and will be confirmed during the pilot. Without a GPU on the same server, the models can run on a separate GPU server in your network.
How it installs
- We send you the release. A download token that can only fetch isobata releases, a licence file and, separately, our public signing key.
- Check the signature. You verify the release package against our key before unpacking it.
- Fill in the settings. The address your team will open, the certificate (Let's Encrypt, your own, or a self-signed one for trials), and the read-only tokens for your code host and Figma.
- Run the install command. It checks that every image is signed with our key, downloads the images and the models (about 20 GB the first time), starts everything and runs a test: the web app loads, the services and models are healthy, and the administration endpoints are not reachable from the network.
- Index your projects. Choose the repositories, or a whole group, and the Figma files. Your team can ask questions as soon as indexing finishes.
Running it
| Task | How |
|---|---|
| Upgrade | Download and verify the new release, then one command. It checks the signatures, takes a backup, starts the new version and tests it; if anything fails it returns to the previous version by itself. |
| Roll back | One command returns to the previous release. |
| Back up and restore | One command each. Schedule the backup daily and copy it off the server. |
| Renew the licence | Replace the licence file. The services pick it up within ten minutes, with no restart. |
| Review outbound calls | Every request to the outside, allowed or refused, is in the egress proxy's log. |
| Check health | One command shows each service's state and the licence; a test command checks the installation end to end. |
What runs on the server, what it can reach and how releases are checked: Security and architecture. Which models it runs: AI models.
The pilot includes help with installation, from sizing the server to indexing your first projects.
Apply for the pilot