Loading
Loading
PixelCity is not a marketplace for someone else’s cloud. We operate five production services on our own hardware, with clearly separated duties and a single login for everything.
We started with a single goal: run our own services where the data stays without detours. One server, one mailbox, one VPN — and the frustration of vetting every single offering with a third-party provider.
Today five production services run on our own hardware in the EU. Each one has a status page, documentation, and a human who answers. The tech is deliberately boring: open-source software, containers, one machine per service, backups on separate hardware.
What has not changed is responsibility. When something breaks, the team that operates it deals with it. There is no contractor to pass it on to.
„A service we cannot explain is a service we should not operate.“
No brokering, no pass-through to third parties. The hardware sits in the European Union and the data stays there.
Stalwart, Vaultwarden, SearXNG, Keycloak and TeamSpeak — all open source, all with documented interfaces.
One identity for every service. No consolidated bills, no hidden line items, prices in euro in plain sight.
Support in German and English, usually within one business day. Security reports go straight to the security contact.
One own machine in the EU, one mailbox, one VPN. The beginning of everything.
Webmail, vault, search, identity and voice run as separate services on separate containers.
Keycloak replaces the individual logins. OAuth 2.0 ties every service to one identity.
Our own tunnel CLI, a public REST API, the marketplace, and a status endpoint anyone can query.
We do not hold certifications we do not have. What we have, we say openly — including what is still in progress.
Processing on our own EU hardware, data processing agreements with every sub-processor, no tracking on this website.
Technical and organisational measures documented, data processing agreements signed with every sub-processor.
The ISMS build-out is running; certification is planned for 2027. The current status is published here.
External security reviews of the public endpoints, results available on request in summarised form.
A small team of operations and development. Whoever answers you also operates the services you write about.
Responsible for availability, updates and recovery — with a documented four-hour RTO.
Builds and maintains the CLI, the REST API and the integrations between services.
First point of contact for questions, invoices and security reports — with direct escalation to development.
Startup, agency or home office: write to us and tell us what you need.