Transparency
We publish our node inventory, so anyone can see what we operate (country, type, count) without us hiding behind marketing claims.
ZATVA / ABOUT
About ZATVA
ZATVA is a DevOps / DataOps / SysAdmin team that runs infrastructure for Web3, AI, ZK and DePIN projects. We also run our own fleet of 50+ nodes as our proving ground, because we'd rather sharpen the discipline on our own infra before we bring it to clients.
Our approach
Three principles shape how we run infrastructure, and they are not slogans, because each one shows up directly in how we operate and what we publish.
Geographic redundancy
5+ countries across Europe, the Americas, and APAC, so there's no single-region risk and no single-AZ blast radius for client workloads.
Production-grade ops
24/7 monitoring, slashing-aware playbooks, structured incident response, and runbooks for everything. This isn't "best effort", it's engineered.
Where we operate
Our fleet spans 5+ countries, and the distribution is intentional, because we want regulatory diversity, network-route diversity, and time-zone coverage for follow-the-sun on-call. See full per-country counts on the geo distribution section of the homepage.
🇦🇹 AT
🇦🇺 AU
🇧🇪 BE
🇧🇬 BG
🇧🇷 BR
🇨🇦 CA
🇨🇿 CZ
🇩🇪 DE
🇫🇮 FI
🇷🇺 RU
🇬🇧 UK
🇺🇸 US
Why we publish our node inventory
Transparency is the differentiator in DePIN. A lot of operators claim uptime and global reach with no way to verify either, so we took the opposite stance: a public, regularly-updated spreadsheet showing country, node type, and count for every host we run.
What we do not publish is hostnames, IPs, customer-specific assignments, or validator addresses, since operational security still matters and only the shape of the fleet is public. We laid out the full reasoning in our blog post: Why we publish our node inventory.
Team
We're a small distributed team, and each engineer owns one or more ICP. We rotate follow-the-sun, handing off every 8 hours, so on every call you talk to an engineer, never to sales. Full roster: /team/.
@drxim
UTC+3
Founder, DevOps lead. 12 years SRE, AI / LLM ops, DePIN.
@shell
UTC+0
Co-founder. SRE. Kubernetes, validators, Terraform.
@serg
UTC-5
SRE, ZK provers and DePIN.
We don't run sales funnels or account managers. If you reach out about a workload you'll talk to an engineer who can answer questions about slashing protection, k8s rollouts, GPU memory sizing or archive-node storage layout on the first message.
Contact
Pick the channel that fits. We respond within 24 hours, usually much faster during CET business hours.
✉ Message
Web form, replies via your preferred channel.
Telegram
Direct DM. Fastest for ops chatter.
For teams that already operate there.
Company updates and direct messages.
Discord
DM the on-call engineer.
Threads, questions, public answers.
GitHub
Code, issues, public configs.
Slack
Shared channels for active clients.