256GB of memory on every GPU. Launch 1, 2, 4 or 8 from the console or the CLI and pay per second while they run.
A job that needs three 80GB cards and a sharding config fits on one device.
$2.99 per GPU on a full node. Billed per second from prepaid credit. A stopped instance is not billed for compute.
The console shows what is available and holds it when you launch. The CLI launches the same instance from a script.
Memory capacity decides whether a model fits. MI325X carries 256GB on a single card, so work that would be split across three 80GB GPUs runs on one, with no sharding config and no interconnect to tune.
A full node holds eight: 2,048GB of GPU memory, 64 vCPUs and 2,048GB of system RAM in one instance, with 6.0 TB/s of memory bandwidth per card.
A fine-tune runs for hours or days and then stops. Billing is per second and ends when the container does, so between jobs you pay for stored volumes and nothing else.
Adapt an open model to your own data. Start from the PyTorch (ROCm) template, write checkpoints to a network volume, and stop the instance when the run ends.
Take a full node: eight GPUs and 2,048GB in one instance. Checkpoints on a network volume survive a stop, a restart and a deleted instance.
Run your own workload on MI325X before you commit to it. Serve it with the vLLM (ROCm) template behind a public HTTPS port. If it holds up, managed GPU is the same hardware.
Submit one command as a Run Job from the CLI. It streams output back and releases the GPU when the command exits. You pay only while the command runs.
$3.19 at two GPUs, $3.09 at four, $2.99 at eight. Metered per second from prepaid credit. The rate you launch at holds for that instance, and there is no contract.
Add credit by card and pay per second while the container runs. Waiting for capacity and pulling the image are free. A stopped instance is not billed for compute.
Beta prices as of 19 November 2026. Each GPU comes with 8 vCPUs and 256GB of system RAM. Container disk costs $0.30 per GiB a month while the instance runs. Network volumes cost $0.30 per GB a month until you delete them.
DigitalOcean rate from its published pricing, checked 19 November 2026.
Three H100s hold 240GB for $13.77 an hour. One MI325X holds 256GB for $3.29. Lambda rate from its published pricing, checked 19 November 2026.
Use your Featherless account or create one, then add credit by card. One hour of an instance's rate is enough to start it.
PyTorch, vLLM and SGLang templates ship with ROCm, SSH and JupyterLab, or bring your own linux/amd64 image. Choose 1, 2, 4 or 8 GPUs and mount a network volume for anything you want to keep.
SSH in as root, open the browser terminal, or work in JupyterLab. Stop the instance when the job ends and compute billing ends with it.
If nothing in it depends on CUDA-only code, generally yes. The PyTorch (ROCm) template ships Python 3.12, PyTorch 2.12 and the ROCm libraries. PyTorch's torch.cuda API drives the GPU through ROCm, so torch.cuda.is_available() returns True. A hard CUDA dependency is the one deal-breaker, because the port costs more than the rate saves. If you are unsure about a library, ask in Discord before you add credit.
On memory, 256GB per GPU against 80GB on an H100 and 141GB on an H200. We have not measured throughput against either, so we do not quote it. Billing is per second: ten minutes of your own job on one GPU costs about 55 cents.
No. One instance or Run Job uses up to eight GPUs on a single node, 2,048GB in total. You can run several side by side, up to 16 GPUs per organization by default, and ask in Discord for a higher limit.
Not on GPU Cloud. That is fine for a training run and wrong for production traffic with a latency target. If you need an uptime commitment, managed GPU is the product, and it runs on the same hardware.
We maintain three ROCm templates, PyTorch, vLLM and SGLang, each with SSH and JupyterLab. Everything after launch is yours: the model, the settings and the job. If you want a model catalog behind an API, that is our serverless inference product.
Not from a running instance. It sits on dedicated compute until you stop it or your credit runs out. If you stop it, starting again needs a free GPU of the same model, which can fail when capacity is short. Run Jobs are different: they stop at 24 hours and can be interrupted to make room for other work, so allow retries and write checkpoints to a network volume.
No. It is your data and we do not read it. We monitor metadata only, to catch abuse such as someone attacking a third party from our network. Files on a network volume stay on our disks until you delete the volume, so we have legal obligations and would cooperate with a lawful request.
Usage is metered per second from the moment the container starts. Waiting for capacity and downloading the image are not billed. A stopped instance is not billed for compute, and its container disk bills only while it runs. Network volumes bill for their full size from creation until you delete them.
The container disk is erased on every stop and restart, installed packages included. Keep datasets, checkpoints and the Hugging Face cache on a network volume. A volume keeps its data when the instance stops or is deleted, can grow while mounted, and can be shared by several instances.
There is no commitment. An instance starts once your credit covers one hour of its rate, which is $3.29 for one GPU. After that you pay per second.
The region and egress pricing. If either decides it for you, ask in Discord or email gpu@featherless.ai before you add credit.
Sign in with your Featherless account, add credit and launch. The quickstart covers sign-in, launch, running code and clean-up.
If you are moving an inference workload or need more than 16 GPUs, talk to us about managed GPU or a higher limit.