About

Tignex is an independent open-source organization that develops tools, infrastructure, protocols, standards, libraries and system components for developers and software teams. Its purpose is to produce software that gives developers more control, takes interoperability seriously, creates no unnecessary vendor lock-in, and can be self-hosted when that is what a team needs.

It is not tied to a single product, programming language or technology. What holds it together is a way of working — transparent behaviour, solid engineering, a production-oriented bias and a preference for practical problem solving over ambitious architecture.

What we work on

• Open-source developer tools
• Protocols and specifications
• CLI tools
• Server software
• Runtime components
• Libraries
• Infrastructure projects

The list is deliberately open-ended. A new category is added when a problem turns out to need one, not to fill out a catalogue.

How the projects relate

Projects under Tignex keep their own names, identities and domains. Tignex is their shared engineering organization and publisher — the place the standards, the review habits and the release discipline come from, not a brand stamped on the front of each one.

That separation is the point. A project should be adoptable on its own merits, without adopting an ecosystem, and it should survive anything that happens to the organization that published it.

Who is behind it

Tignex is run by Muhammet Şafak, a staff engineer who has been building software since 2008 and designs the microservice and event-driven architecture of high-traffic systems. He works across the PHP, Go, Python and JavaScript ecosystems — a developer who focuses on the problem rather than the language, which is most of the reason a project like BabelQueue exists at all.

He is the founder of CommitBrief and BabelQueue, and writes at sade.dev.

Questions, corrections and contributions are all welcome: write to info@muhammetsafak.com.tr, or open an issue on the project you are reading about.