About Virebent.art
Who runs this, why it exists, and what we won't do.
What this is
Virebent.art is a personal privacy infrastructure project. It started as a single server running a few self-hosted alternatives to corporate tools and grew into a small suite of services covering communication, collaboration, anonymous publishing, and anonymous networking.
This is a personal project with no corporate structure behind it. We run servers, write code, and try to keep things working. If something breaks we fix it. If a service becomes unsustainable we say so and shut it down cleanly.
The people here come from a background in privacy tooling, anonymous remailers, and decentralized network infrastructure. That background shapes every decision about how services are deployed and configured.
Principles
- Minimal metadata by design. Logs are kept only as long as operationally required, then deleted.
- Every asset on every page is served from our own servers. No external fonts, CDN, or third-party scripts.
- Open source software throughout. Every piece of software we run has a public codebase we can audit and modify.
- Infrastructure on hardware we physically control — not rented from surveillance-adjacent cloud providers.
- TLS 1.3 with modern cipher suites only. Older protocol versions are disabled.
- Pages load without executing tracking code, telemetry, or analytics of any kind.
- Revenue comes from voluntary contributions, not from selling access to users.
Anti-crawler policy
We maintain a robots.txt that blocks Google, Bing, Yandex,
and most commercial crawlers. This is intentional. We don't want our
infrastructure indexed by advertising platforms or used to train
commercial AI models.
We permit DuckDuckGo, because it respects user privacy and doesn't build advertising profiles. We also permit legitimate privacy-respecting search engines that make similar commitments.
If you run a crawler for non-commercial, non-surveillance purposes and want to be permitted, reach out via the contact page.
Mailing list
We run a low-traffic mailing list. Typical volume is a few messages per month: service announcements, occasional essays, and security notices. Sent directly from our own server. Plain text, honest subject lines, unsubscribe link in every message.
Technical stack
All services run on self-managed Linux servers hosted on Proxmox VE, with workloads isolated in unprivileged LXC containers. Podman handles additional containerized services; NGINX acts as reverse proxy with TLS 1.3; certificates come from Let's Encrypt. The full stack is under our direct control with no external SaaS dependencies.
Custom code is written in PHP or Go. Static pages are plain HTML and CSS — a text editor and a browser are sufficient to read and verify everything.