The people accountable for our systems
Titan Software is run by its members — engineers, security researchers and operators who take ownership of specific systems. Listed here are members who have opted into public listing.
Vojtěch
Chairman & Infrastructure Lead
Responsible for the association's technical strategy, production infrastructure and Titan Security platform direction.
Engineering specializations
Responsible for
Martin
Lead Software Engineer
Responsible for software architecture and detection systems.
Engineering specializations
Responsible for
Tomáš
Community Director
Responsible for community coordination, partnerships and documentation.
Engineering specializations
Responsible for
Engineering leadership
Titan Software is run by its members. Each engineering area has a single technical owner accountable for its long-term quality.
Leadership
Chairman
Vojtěch
Chairman & Infrastructure Lead
Engineering areas
Infrastructure & Network
Vojtěch
Chairman & Infrastructure Lead
Software Engineering
Martin
Lead Software Engineer
Community
Tomáš
Community Director
Delivery
Projects
Titan Security · Titan AC · CFXR
Every system has an owner
Every production system has a clearly assigned technical owner — the person accountable for its reliability, security and maintenance.
Titan Security
Owner
Vojtěch
Chairman & Infrastructure Lead
Titan AC
Owner
Martin
Lead Software Engineer
CFX Resolver
Owner
Vojtěch
Chairman & Infrastructure Lead
Infrastructure
Owner
Vojtěch
Chairman & Infrastructure Lead
Network
Owner
Vojtěch
Chairman & Infrastructure Lead
Monitoring
Owner
Vojtěch
Chairman & Infrastructure Lead
Website
Owner
Vojtěch
Chairman & Infrastructure Lead
Documentation
Owner
Tomáš
Community Director
Community
Owner
Tomáš
Community Director
Engineering principles
The standards we hold every system to, regardless of who owns it.
Security by design
Threat modeling and hardening come before features, not after an incident.
Infrastructure as code
Every server and service is provisioned from version-controlled, reviewed code.
Automation first
If a task is done twice by hand, it becomes a script or a pipeline.
Documentation first
A system isn't done until someone else could run it from the docs alone.
Operational excellence
We optimize for the day a system fails, not only the day it ships.
Monitor everything
Metrics, logs and alerts on every node — we see problems before users do.
Peer review
Changes to production are reviewed by someone other than their author.
Long-term maintainability
We favour boring, well-understood technology we can still run in five years.
Transparent decisions
Technical decisions are documented and open to the people they affect.
Open engineering
We develop in the open so the ecosystem can inspect and build on our work.
Why engineering leadership?
Our structure is a deliberate answer to a simple question: who is accountable when it matters?
Titan Software is not owned by shareholders. It is a registered association governed by its members, so no one is owed a return at the expense of the systems or the people who depend on them.
Every engineering area has a technical owner responsible for its long-term quality — accountability sits with a named person, not a committee. Revenue is reinvested into engineering and infrastructure rather than distributed.
Leadership here exists to coordinate engineering work and represent the association, not to build a corporate hierarchy. Titles describe responsibility, not rank.
Work with us
Whether you operate a community, represent a partner organization, or want to contribute as a member of the association — we would like to hear from you.