Operating since March 11, 2020

2020, and every year since

Incognito VPS started because two people could not get a merchant account for an offshore hosting company. Being forced to take crypto only, from day one, turned out to be the best constraint we ever had — it removed the chargeback problem, which removed the reason to know who our customers are.

Answer

Incognito VPS began operating in March 2020 with two racks in Sofia and one in Amsterdam. It now runs 19 facilities across 16 locations under AS204287, has deployed over 41,800 servers, and publishes its full incident history including the outages.

41,800

servers deployed

16

locations

19

facilities

AS204287

autonomous system

14

IPv4 prefixes

4.2 Tbps

edge capacity

§01 Build-out

Six years, dated

Including the two outages that changed how we operate. A company history with no failures in it is not a history.

Incident log
  1. launch

    Incognito VPS begins operating

    Two racks in Sofia, one in Amsterdam, forty-one customers in the first month. Crypto-only from day one because the founders could not get a merchant account for an offshore hosting company, which turned out to be the best constraint we ever had.

  2. network

    Reykjavík comes online

    RVK-1 in Hafnarfjörður, chosen for the IMMI framework and the geothermal power. First location where we published a legal dossier with statute citations rather than adjectives — it became the template for all the others.

  3. product

    Token-only accounts replace email signup

    The email field is removed from the schema entirely, not made optional. Existing accounts migrated to tokens over six weeks. This is the change that defined what the company is.

  4. network

    AS204287 announced

    Our own autonomous system number and first /22 allocation. Owning address space is what makes the clean-IP guarantee possible — you cannot promise the reputation of a range you rent from someone else.

  5. network

    Zürich and Panama City

    ZRH-2 and PTY-1 open within three weeks of each other, adding a dual-criminality jurisdiction and a no-MLAT jurisdiction to the map at the same time.

  6. legal

    First warrant canary published

    Quarterly, PGP-signed, with the current Bitcoin block hash embedded so that it cannot be pre-signed in bulk. Unbroken since.

  7. incident

    AMS-3 core switch failure

    A failed line card took 40% of Amsterdam offline for 3 hours 12 minutes. The spare was in the wrong facility. We published the post-mortem the same week and now hold spares for every chassis on site at every location.

  8. network

    Chișinău and Bucharest

    KIV-1 and OTP-1 open. Moldova gives a non-EU jurisdiction at EU latency; Romania gives the strongest anti-retention court precedent in the union.

  9. product

    Windows RDP line launches

    Desktop-class Core i9 and Ryzen 9 hosts rather than server silicon, because RDP responsiveness is single-thread bound and a 5.7 GHz boost is what makes a session feel local.

  10. legal

    First transparency report

    Legal requests by jurisdiction, how many produced data, and what that data consisted of. The answer to the last question has been "a token hash and a balance" every quarter since, because that is all there is.

  11. network

    Moscow opens

    MOW-2, with the most heavily caveated location page on the site. Russia removes Western legal reach and adds Russian legal reach including mandatory SORM interception. We say so on the page rather than in the fine print.

  12. product

    GPU line launches

    RTX 4090 first, in Amsterdam and Reykjavík. Iceland turned out to be the right answer for long training runs — free ambient cooling most of the year and entirely renewable power.

  13. product

    Storage servers

    Four to thirty-two terabytes of RAID-10 with unmetered transfer. Built because customers kept buying dedicated servers purely for the disk and paying for cores they never used.

  14. incident

    Sofia power event

    A utility failure plus a generator that failed to transfer took SOF-1 down for 47 minutes. Automatic SLA credits were applied to every affected account without anyone having to ask. Transfer switches are now tested monthly under load rather than quarterly at idle.

  15. product

    H100 SXM5 capacity

    Hopper-class GPUs in Reykjavík and Amsterdam, including a four-card NVLink configuration. Still the only no-KYC H100 capacity we are aware of.

  16. product

    Machine-readable commerce layer

    Agent card, OpenAPI 3.1 document and an MCP endpoint. Removing the identity layer for privacy reasons had, without anyone planning it, produced the cleanest agent-purchasable checkout on the market.

  17. network

    IPv6 /48 allocations become free

    Every server already shipped with a routed /64. Customers running container fleets kept asking for more, so we stopped charging for the /48.

  18. network

    Eighth jurisdiction: Sofia expansion and full LUKS-at-provision

    SOF-1 doubles in capacity and LUKS2 keyed at first boot becomes available at provision on every dedicated, GPU and storage plan at no charge.

§02 Commitments

Four things that will not change

01

We will never add a card payment option

Cards bring chargeback liability, chargeback liability forces identity collection, and identity collection defeats the product. This is not a preference we might revisit under commercial pressure — it is the load-bearing constraint the rest of the design rests on.

02

We will never add analytics to this site

No Google Analytics, no tag manager, no session recording, no third-party font. The site makes zero external requests and you can confirm that in your browser in ten seconds. A privacy host that ships surveillance on its marketing pages has told you what it actually thinks.

03

We will not pretend to be beyond the law

We operate real companies in real countries and we comply with valid orders from those countries. What we changed is what such an order can produce: a token hash and a balance. Providers claiming they would refuse a valid order have either never received one or are not being straight with you.

04

We will keep publishing the bad quarters

The 2021 Amsterdam outage is on the home page. The 2024 Sofia generator failure is in the incident log. Uptime figures without an incident log behind them are marketing, and we would rather be the company that publishes both.

§03 Footprint

Where the hardware is

All locations

55-second deploy

Pick a jurisdiction. Pay in crypto. Be running in a minute.

No account to create, no email to confirm, no card to enter.