Advanced
Containers, without the Project around them.
Most apps belong in a Project: you connect a repository and Sarpius builds it, routes it and runs it. SparxLite is for the rest. You pick an image, the resources and the ports, and it runs. No repository, no build step, no components.
Billed per minute, from the same wallet.
Which one
Not everything should be a Project.
Reach for SparxLite when
- You already have an image and there is no repository to build from.
- It is a process rather than an application: a game server, a bot, a worker you drive yourself.
- You need specific ports addressed directly, not only HTTP behind a router.
- You want to run something for an afternoon and then turn it off.
Reach for a Project when
- The thing you are deploying lives in a git repository.
- You want a push to your branch to be the deploy.
- It needs a database, a bucket, a domain and TLS wired to it.
- It is an application, not a single process.
Both bill to the same wallet, and you can run both on one account.
Getting there
Three choices and it is running.
There is no repository to connect, no build to configure and no framework to detect. You answer three questions and the container exists.
01
Pick an image
Start from the catalogue or bring your own. Nothing is inferred on your behalf and nothing is rewritten.
02
Pick the size
CPU, memory and storage. Change it later without rebuilding anything around it.
03
Start it
Ports are allocated, the console attaches, and the per-minute meter starts. Stop it whenever you want.
What you control
The parts a build pipeline would have chosen for you.
01
The image
Any container image. Bring your own or start from the catalogue. Nothing is detected, inferred or rewritten on your behalf.
02
The resources
CPU, memory and storage per instance. Resize when the workload changes rather than rebuilding around it.
03
The ports
Allocations you can address directly. Useful for anything that is not a web server behind a reverse proxy.
04
The lifecycle
Start it and stop it yourself. There is no pipeline deciding when it rebuilds and no push that redeploys it underneath you.
The console
Everything you need to actually run it.
A container you cannot reach into is not much use. All of this is in the browser, on the container you just started.
A live console
Attach to the running container, watch its output as it happens, and type commands straight into it.
Power control
Start, stop, restart and kill, by hand. No pipeline decides when your process goes down.
Files
Browse, edit, upload, download, rename, archive and extract in the browser. SFTP when you would rather use your own tools.
Databases
Create a database against the container, rotate its password, drop it when you are done. Nothing separate to wire up.
Sub-users
Give someone access to one container without handing over your account.
Live stats
CPU, memory and storage while it runs, not a report you read afterwards.
Billing
Per minute, from the wallet you already have.
SparxLite draws from the same prepaid balance as the rest of your account and sits under the same spend cap. There is no separate plan, no separate invoice and no minimum term. The rate depends on the instance size you pick, and you see it before you start.
See the pricingWhere it runs
One zone, in the Netherlands.
Sarpius runs in a single zone today, in the Netherlands, under EU ownership. Not a European region of a company headquartered somewhere else. If your workload has to sit in a specific place outside the EU, this is not the platform for it, and we would rather tell you here than after you have signed up.
Start one and stop it again.
A container is running a minute from now, and nothing else has to change.