About
Why this exists, and who is making it
Tulpar is team chat you run on your own machine. This page is the part that is usually left off: why it is being built, who is building it, how it is paid for, and what is not done.
The problem it was built for
Team chat became infrastructure. It is where decisions get made, where incidents get run, and where most of what an organization knows ends up living. Then that infrastructure moved onto somebody else's machine and started charging by the head.
The self-hosted alternatives exist, and some of them are good. What they mostly do is hold the interesting parts back for a paid tier, or make you run one client per server. Neither of those is a technical limit. Both are a pricing decision wearing a technical costume.
What we decided instead
One installation carries as many workspaces as an organization needs, and one client holds every server a person is trusted on. That is the shape of the data model rather than a feature bolted onto a desktop app, which is why it works the same on the web and on the phone.
Nothing is held back. Tulpar Enterprise is the same software with work attached: deployment, migration off whatever you run today, and support with a name on it. There is no build with the good parts removed.
How it is paid for
By the Enterprise work, and only by that. There is no per-seat fee, no seat count to report, and no analytics package anywhere in the client or the server to count them with.
That matters for a reason beyond price. A product paid for by seats has a reason to want your directory; a product paid for by deployment work does not.
Who is behind it
Tulpar is built by Ali Gündoğdu / Projekod Yazılım, based in Pamukkale, Denizli, Türkiye.
The repository is closed today and will open: the source ships under FSL 1.1. On that day one answer to "who is behind it" becomes: whoever reads it. That is the only claim on this site that will not need us.
What is not done
Push notifications are not finished. Plugin PHP is not sandboxed, and plugin packages carry a checksum rather than a signature.
No compliance certification is claimed anywhere on this site, because none has been obtained.