Spin up virtual machines or containers for anything from a background worker to a full production service — scale up, scale down, or scale to zero, all from one console.
Whether you need one small instance or a fleet that scales with traffic, the setup is the same: pick a size, pick a region, connect.
A production-ready server from your very first deploy, with room to grow into an auto-scaling fleet.
Long-running processes that consume jobs off a queue, without the execution-time limits of a function.
Deploy your own Docker images directly, with private networking between services on the same account.
Spin up short-lived instances to test a branch or a release, then tear them down without a lingering bill.
No add-ons to configure and no extra invoices — this is what every instance comes with.
SSH in and configure the box however your workload needs — nothing is locked down on our end.
Set a min and max instance count and let traffic decide the rest — no manual resizing at 2am.
Deploy closer to your users, or spread a fleet across regions for redundancy.
Take a full disk snapshot before a risky change, and roll back in a couple of clicks if it goes wrong.
Instances on the same account can talk to each other over a private network, not the public internet.
CPU, memory, and disk metrics from the console — nothing extra to install or wire up.
No infrastructure to configure first. Pick what you need and we handle provisioning, networking, and security in the background.
Typed clients across the languages you already use — same primitives, idiomatic in each one. If you're not the one writing this part, feel free to skip ahead to pricing.
// Provision a compute instance
import { WinixxCloud } from '@winixx/cloud';
const cloud = new WinixxCloud({ apiKey: process.env.WINIXX_API_KEY });
const instance = await cloud.compute.create({
name: 'api-prod-1',
size: '2vcpu-4gb',
image: 'ubuntu-24-04',
region: 'us-east',
});// Provision a compute instance via the REST API
const res = await fetch('https://api.winixx.net/cloud/v1/compute', {
method: 'POST',
headers: {
'Authorization': `Bearer ${WINIXX_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
name: 'api-prod-1',
size: '2vcpu-4gb',
region: 'us-east',
}),
});
const instance = await res.json();// Provision a compute instance
import { WinixxCloud, ComputeSpec } from '@winixx/cloud';
const cloud = new WinixxCloud({ apiKey: process.env.WINIXX_API_KEY! });
const spec: ComputeSpec = {
name: 'api-prod-1',
size: '2vcpu-4gb',
image: 'ubuntu-24-04',
region: 'us-east',
};
const instance = await cloud.compute.create(spec);# Provision a compute instance
from winixx_cloud import WinixxCloud
cloud = WinixxCloud(api_key=os.environ["WINIXX_API_KEY"])
instance = cloud.compute.create(
name="api-prod-1",
size="2vcpu-4gb",
image="ubuntu-24-04",
region="us-east",
)// Provision a compute instance
use Winixx\Cloud\WinixxCloud;
$cloud = new WinixxCloud(apiKey: getenv('WINIXX_API_KEY'));
$instance = $cloud->compute->create([
'name' => 'api-prod-1',
'size' => '2vcpu-4gb',
'image' => 'ubuntu-24-04',
'region' => 'us-east',
]);// Provision a compute instance
import net.winixx.cloud.WinixxCloud;
import net.winixx.cloud.model.ComputeSpec;
WinixxCloud cloud = new WinixxCloud(System.getenv("WINIXX_API_KEY"));
ComputeHandle instance = cloud.compute().create(
ComputeSpec.builder()
.name("api-prod-1")
.size("2vcpu-4gb")
.image("ubuntu-24-04")
.region("us-east")
.build()
);// Provision a compute instance
#include <winixx/cloud.hpp>
winixx::Cloud cloud(std::getenv("WINIXX_API_KEY"));
winixx::ComputeSpec spec;
spec.name = "api-prod-1";
spec.size = "2vcpu-4gb";
spec.image = "ubuntu-24-04";
spec.region = "us-east";
auto instance = cloud.compute().create(spec);// Provision a compute instance
using Winixx.Cloud;
var cloud = new WinixxCloud(Environment.GetEnvironmentVariable("WINIXX_API_KEY"));
var instance = await cloud.Compute.CreateAsync(new ComputeSpec {
Name = "api-prod-1",
Size = "2vcpu-4gb",
Image = "ubuntu-24-04",
Region = "us-east"
});For side projects, small scripts, and light background work.
For live products with real traffic and room to scale.
For teams with compliance needs, dedicated hardware, or scale.
| Feature | Starter | Growth | Enterprise |
|---|---|---|---|
| vCPU | 1 | 2 | Custom |
| Memory | 1 GB | 4 GB | Custom |
| SSD storage | 25 GB | 80 GB | Custom |
| Bandwidth | 1 TB | 4 TB | Custom |
| Auto-scaling | — | ✓ | ✓ |
| Private networking | — | ✓ | ✓ |
| SLA | — | — | ✓ |
| Support | Community | Standard | Premium |
"We moved our staging and prod databases over in an afternoon. Having compute, database, and functions under one identity layer removed a whole category of glue code."
Alex MeyerStandard Linux distributions like Ubuntu and Debian, plus support for bringing your own Docker image if you'd rather deploy a container than configure a bare OS.
Yes — point Compute at your own image and it runs the same way a VM-based deploy would, with the same networking, snapshots, and monitoring underneath.
Set a minimum and maximum instance count for a group, and Winixx Cloud adds or removes instances based on load — no manual intervention needed during a traffic spike.
Yes, static IPs are available on Growth and Enterprise plans, and can be reassigned between instances without any DNS changes on your end.
That's handled by our AI / ML product rather than general-purpose Compute — talk to sales and we'll help you figure out which one actually fits your workload.