Skip to content

Cloud

Compute in Amsterdam. Protected before the first packet.

Virtual machines on our own platform, on our own network. In production today, carrying our own workloads and those of a small group of early users.

Request accessLiveAccess on request

3D illustration: a close view of a row of server racks, their status lights on.

Building blocks

The parts you expect from a cloud. Without the sprawl.

Instances, the networking around them, and private connectivity between your own servers. The model you already know.

kvm

Instances

KVM virtual machines.

Full root access. Yours to run as you see fit.

L2private

Private networks

Layer 2 between your servers.

Your own machines talk privately, at no extra charge.

:443:8443nat

NAT

Port forwarding you control.

Keep instances behind a shared address and forward only what you choose.

lb

Load balancers

Spread the traffic.

Distribute connections across instances from inside the platform.

vpntiertier

VPC and VPN

Isolated tiers, private access.

Separate network tiers, and a private way into them.

inline

Protection

BitsNull, included.

In front of every public address. On by default.

This is the model the platform is built around. Tell us which parts you need and we will confirm what is available to you today. Public self-service ordering is in development.

Specification

The facts, without a brochure.

location
Amsterdam, NetherlandsOne location today.
hypervisor
KVM
orchestration
Apache CloudStack
network
AS219148Our own autonomous system.
ddos protection
BitsNull, inlineIncluded on every public address.
port policy
No restrictionsAny protocol on any port. Protection is tuned per service.
ordering
On requestSelf-service is in development.

Who it is for

Built for workloads that cannot afford to disappear.

How protection works
  1. 01

    Developers and small teams who want European compute with real protection and a usable panel, without hyperscaler complexity.

  2. 02

    Projects that get attacked. Game servers, communities, event networks and small hosters. Protection is the reason they come.

  3. 03

    Anyone running something unusual. A custom protocol on an odd port is not a support ticket here. It is a filter profile.

Tell us what you need to run.

Access is opened by hand while self-service is being built. Describe the workload and we will tell you plainly whether we are the right place for it.