What's included & limits
BareMeta is a paid Linux VPS console for early-access customers. This page states what you get today, what is still maturing, and the conservative limits that apply while the platform scales.
Early access position
- Single UK region â one datacentre footprint at launch; no multi-region picker.
- Real infrastructure â you pay for KVM virtual machines on dedicated host hardware, not a demo sandbox.
- Business-hours support â in-console tickets with operator follow-up during UK business hours unless an incident needs best-effort escalation.
- No high-availability promise â we do not claim multi-host failover or carrier-grade SLAs until that architecture is engineered and tested.
- Honest boundaries â maintenance windows, suspension for unpaid accounts, and conservative quotas are normal while operations mature.
What's included today
Authoritative pricing for a new server is always the total shown in the Launch instance wizard before you confirm. See Understanding billing for how hourly usage, bandwidth, and invoices work.
Not included yet
These are common on larger clouds but are not part of paid early access unless explicitly agreed in writing:
- Managed VM backups â customer backup/restore controls are not offered in the console today.
- Load balancers, managed databases, object storage, Kubernetes â VPS-only scope at launch.
- Multi-region or infrastructure tier selection â one UK footprint; hardware class is disclosed read-only in the wizard, not selectable.
- High availability / multi-host failover â single-hypervisor operations until a split control plane exists.
- Email team invitations â team adds require an existing BareMeta username.
- One-click OS rebuild in place â create a new instance or restore from your own exports/snapshots.
- Guaranteed backup/restore SLA â restore times are best-effort unless a stronger SLA is published later.
Platform limits
Limits below are conservative defaults for public early access. Per-project quotas set by operators can be lower. The console and API enforce the stricter of published caps and your project quota.
Compute & storage
| Item | Public default | Notes |
|---|---|---|
| Predefined plans | Starter â Large families | Port speed and included outbound bandwidth vary by plan â see billing guide. |
| Custom size (vCPUs) | 1 â 16 | Wizard sliders; larger sizes require support. |
| Custom size (RAM) | 512 MB â 64 GB | Same caps as the launch wizard. |
| Custom size (disk) | 10 GB â 1 TB | Disk can be grown on resize where supported. |
| VMs per project | Operator quota | quota_vms on the project; 0 = use platform default policy. |
| Snapshots | Per-VM, in-console | Stored on host; not off-site backup. |
| Disk exports | Async, rate-limited | Large exports may queue; not a backup service. |
Networking & access
| Item | Public default | Notes |
|---|---|---|
| Region | United Kingdom | Single datacentre footprint at launch. |
| Public IPv4 | Pool-based | Availability depends on networking mode. When public routed IPs are enabled, allocation follows datacentre pool policy â typically one public IPv4 per user/project; extras need operator approval. See Networking model. |
| Outbound SMTP (:25) | Blocked by default | Use an external relay (e.g. Mailgun, SendGrid). Case-by-case unblock via support. |
| Bandwidth overage | Throttled, not billed | After included monthly outbound allowance, throughput drops to 10 Mbps â no surprise bandwidth invoices. |
| Customer VPN | 1 credential per user | WireGuard; readiness-gated. |
| Projects per org | Multiple allowed | Org admins create projects from the tenant switcher or API; each project is a separate private network. |
Account & platform
| Item | Public default | Notes |
|---|---|---|
| ISO uploads | 10 ISOs, 12 GB max each | ISO library UI may be hidden during beta; API limits still apply. |
| Support tickets | Rate-limited | Prevents notification spam; fair use applies. |
| API keys | Org-scoped | Cannot manage human account security or cross-org resources. |
| Unpaid accounts | Suspension + throttle | See billing guide for reminder and suspension timeline. |
Support & reliability expectations
- Support channel: in-console tickets (primary) and billing email for payment issues.
- Hours: UK business hours for routine requests; incident response is best-effort outside those hours.
- Maintenance: scheduled windows may appear in the console banner and on the status page.
- Data responsibility: you are responsible for securing workloads, patching guests, and keeping your own off-platform backups of critical data.
- Uptime: we work to keep the platform available but do not publish a financial SLA during early access.
When limits change
We may tighten or relax limits as capacity and operations mature. Material changes that affect what customers are buying will be reflected on this page and, where appropriate, in console copy or email. The launch wizard and billing views remain authoritative for price and plan-specific bandwidth at the moment you create a server.