Early access is open
Open-source team chat you host yourself. One server carries every workspace your organization needs, and one client holds every server your people work across.
Source-available (FSL 1.1). No per-seat fee, and no seat count to report.
Runs on
A Symfony API, a Go WebSocket server and a Nuxt client, on your PostgreSQL. Web and iPhone are built; what is not, is named on this page.
Why it exists
Memory is not for rent.
A chat tool you use for free walls off your archive one morning. You get to see ten thousand messages; the rest is locked. That is not a technical limit. It is a card held back for the pricing conversation.
And an organization's past is more than the space it takes up in a database. The reasoning behind a decision made under pressure, the tone of a sentence from two years ago, the note written after a mistake. How an organization thinks is kept there.
The alternatives were tried one by one. Each one produced either another version of the same wall or the same answer: the data stays on somebody else's machine. Tulpar was written for that reason.
A tamga is the oldest mark for saying what belongs to whom. It is carved into stone, and carving does not come back off.
The product
Three views of the same running client. Nothing here is a mockup, and nothing is a feature we intend to build.
Web, desktop and mobile. One account, the same servers; whichever you open, you carry on from the same place.
Two different things, and you get both. One installation carries as many workspaces as your organization needs, each with its own channels, members and settings. One client then holds independent servers at the same time: your company, a customer's own installation, a community. Each server opens its own session and its own socket, and all of them sit in the same window. No second application, no second account.
A reply count opens the thread in its own panel while the channel stays where it was. Reactions, follow, per-thread unread and the whole message toolbar come with it, and nothing you were reading moves.
Four palettes ship with the product, each in a light and a dark variant, and the list does not end there: you define your own theme, save it, and export it to hand to somebody else. The reading font and size are a per-person preference rather than a company decision, and the whole interface is available in English and Turkish.
The boundary
The point is not where the software runs. It is that the conversation, the people and the files sit in a database you hold, under a key you made. Here is the whole ledger, both columns, before you think to ask for it.
Your network
Crosses the line
A clay tablet lasted three thousand years because it sat on nobody's server.
A tamga is a mark of ownership. Carved into stone; what is carved is not taken back.
No compliance certification is claimed on this page, because none has been obtained. What is above is the architecture rather than a policy: it holds because of how the software is built, not because of a promise about how it is run.
Shipping today
Not a roadmap, and not a comparison table. Every one of these is in the client you can see in the screenshots above.
Push notifications and signed plugin packages are not finished, so they are not on this page.
Plugins
Plugins are declarative first. A manifest states what the plugin adds and what it is allowed to touch, and the core does the rest. Install one from a directory, a ZIP, or a registry you point the server at.
plugin.json
{ "id": "com.tulpar.dice", "name": "Dice Roller", "type": "slash_command", "capabilities": { "slashCommands": [{ "command": "dice", "usage": "/dice [NdN]" }], "uiExtensions": [{ "slot": "message-toolbar", "icon": "dices", "label": "Roll dice" }] }, "permissions": ["messages.write"] }
A plugin that ships with the product, unedited.
What it does not do, stated here rather than discovered later: plugin PHP is not sandboxed, packages carry a checksum rather than a signature, the registry endpoints exist but the browsing screen does not yet, and a manifest asking to run a bot is rejected. Bots belong outside the request cycle, talking to the incoming webhook endpoint.
Alongside the alternatives
Slack and Mattermost are good software. Where they genuinely do the same thing, the row below says so; the difference is mostly in who holds the database.
On a narrow screen the table keeps all four columns and scrolls sideways rather than dropping two of them.
Nothing on the page ever asks whether something happened. Messages, threads, mentions, reactions, read receipts, typing and presence all travel the same way, the moment they land.
The API writes
Symfony
PostgreSQL announces it
LISTEN / NOTIFY
A Go server pushes
WebSocket
The client has it
Web · iOS
Arm one
Docker Compose on a single host, reachable through a tunnel. No public IP and no open ports. The installer generates the keys, runs the migrations, walks you through the admin wizard and verifies the result. Backups come out as one dated archive.
Arm two
Tulpar Enterprise is the same software with the work attached: deployment on your infrastructure, migration off whatever you are running today, support with a name on it, and the integrations your organization already depends on.
FAQ
What it takes to run, what leaves the building, and what is not finished yet.
Early access
Tulpar opens in waves. Tell us where you would run it and what you are running today, and we will get in touch before the first one.
One email, written by a person. It does not pass through a third-party form service; where it lands is set out on the privacy page.
You are on the list
Your details are with us. We write once, before the first wave opens, and never for anything else.
