Less product, fewer surprises.
We pick a narrow band of problems and build deeply. The studio ships two flagships — Wemote and ObjectX — and nothing it can't support for years.
About Tecknicos
A small studio building infrastructure tools for distributed teams.
Tecknicos was founded in 2016 around one observation: the way most organizations grant access to infrastructure is the workaround, not the work. The studio exists to replace that with something better.
What we believe
Boring problems, treated seriously.
Most infrastructure tools were designed for a world where teams sat in the same building, on the same network, behind the same firewall. That world is gone, and the tools that survived it accumulated workarounds — jump hosts, shared credentials, screen-sharing-as-access.
We build for the world that exists now: distributed teams, third parties who need temporary access, auditors who need real evidence, and engineers who want fewer steps between intent and action.
The studio in one paragraph
Founded 2016. Privately held. Engineering-led — every founder still ships code. Headquartered remotely (which is part of the point). We build a small number of products carefully, and we sell to teams that have to take security seriously because the alternative is genuinely expensive.
Timeline
How we got here.
- 2016
Founded
Tecknicos starts as a small consulting practice helping enterprise teams replace ad-hoc remote access with something policy-aware.
- 2019
Wemote · v0
First internal version of Wemote brokers SSH sessions for design-partner customers, replacing a fleet of bastions.
- 2022
Wemote · public
RDP, VNC, VM console, HTTP/S brokerage land. Wemote becomes the studio's flagship — Tecknicos shifts from services to product-led.
- 2025
ObjectX · public
ObjectX graduates from its design-partner phase to general availability — Tecknicos becomes a two-flagship studio, pairing infrastructure access with identity-object lifecycle governance.
Talk to the builders.
Demos, scoping calls, and design-partner conversations are run by the people who ship code. There is no sales funnel.
API before UI.
If a capability isn't in the API, it doesn't exist. The dashboard is a customer of the same API your CI uses.
Want to work with us?
Design partners, pilots, and serious procurement conversations.
We'd rather have one deep conversation than ten qualifying ones. Tell us what you're trying to do.