How the Kins & Co chat server actually works
A plain-English tour of everything running behind the scenes — no technical background needed.
What is this thing?
Kins & Co is a private community chat — rooms, direct messages, voice and video calls — that runs on a system called Matrix. Think of it like a Discord or WhatsApp that the community owns outright: the software, the message history, the member list, and the rules all live on servers we control, not inside some company's product.
Matrix is an open standard, the way email is. Nobody owns email — Gmail, Outlook, and thousands of other providers all speak the same language and can message each other. Matrix works the same way for chat: our server speaks the standard language, so our members can even chat with people on completely different Matrix servers elsewhere in the world.
Everything described on this page runs as about nine small programs on a cloud hosting platform called Railway — picture renting a few well-managed rooms in a big data-center building instead of keeping a computer humming in someone's closet.
Members only ever see friendly addresses — chat.josiekins.xyz to open the chat app, josiekins.xyz as everyone's username domain. The machinery below is invisible to them, which is exactly the point.
The journey of a single message
When a member types "hello" and hits send, here's the whole trip, end to end. It usually takes well under a second.
The cast of services
The server isn't one big program — it's a small team of specialists, each doing one job well. If one has a bad day, the others keep working.
How you get in: the invite-gated model
Kins & Co is a private club, not a public square. The whole community lives inside one Matrix "space" — think of it as a building full of rooms — and the building's front door is invite-only.
- You're invited. An existing admin invites your account into the community space. There's no open "sign up and wander in" — every member was deliberately let in by a person.
- New arrivals start in the waiting room. Fresh accounts land in a welcome area where DoseBot greets them, points them to the rules, and an admin approves them.
- Once you're in the building, rooms unlock themselves. Each community room is set to "anyone who's a member of the building may enter." No per-room invites, no keys to hand out — membership in the space is the key.
- DoseBot DMs you a map. On approval you get a one-time direct message listing every room and what it's for, so you're never lost.
DoseBot, the caretaker
DoseBot is a program with its own Matrix account that sits in the community 24/7 doing the chores a human moderator would find tedious. Its four jobs:
Welcomes newcomers in the waiting room and the main space, linking them to the rules, introductions, and starter rooms — so a human doesn't have to be awake when someone new arrives.
Sends each newly-approved member a one-time "server map" DM — the tree of every room with a note about what belongs where. It remembers who it has already mapped, so nobody gets spammed twice.
The reconciler: it keeps a written record of how things should be — who's approved, who's banned, who's an admin — and every few minutes compares reality against that record. Anything drifted gets nudged back. A ban evaded or an invite missed doesn't stay wrong for long.
The join-rule gate: on every patrol it checks all ~37 room locks match the invite-gated design — front door invite-only, inner doors members-only. If a lock was accidentally changed, it changes it back automatically and logs what happened.
Voice & video, in one breath
Text messages travel through Synapse, but live audio and video need a specialist — moving thirty pictures a second between five people is a very different job from filing text.
The ticket expires quickly and only works for that one room — so even the call system rides on the same membership rules as everything else.
How it stays healthy without a full-time engineer
Nobody sits watching dashboards all day. Instead, the upkeep is built to run itself — with three habits doing most of the work.
Every service's exact recipe — its software, settings, and startup steps — lives as files in a private code repository (on GitHub). The running server is always built from those blueprints. If a service were ever lost, it could be rebuilt identically; nothing important exists only on the live machine except the databases, which have their own storage.
To change something, you edit the blueprint and save it to the repository. Railway notices, rebuilds only the affected service, health-checks the new copy, and swaps it in. No hand-carrying files onto servers — the blueprint and the building can't drift apart.
An automated probe visits the public endpoints around the clock: is chat answering? is login answering? does the directions file still point the right way? If anything fails, it files an alert ticket automatically — and for a known failure pattern it can even restart the sick service itself.
Every saved change first runs a battery of automatic tests — more than two hundred checks on DoseBot alone, plus consistency checks that the service recipes agree with each other. A change that breaks a rule is rejected before it ever reaches the live server.
Talking to other servers: federation
Because Matrix is an open standard, our server isn't an island. A friend with an account on matrix.org — or any other Matrix server — can be invited into Kins & Co rooms, chat, and call, all from their own account. The two servers exchange messages directly, server-to-server, the way Gmail and Outlook exchange email.
The invite gate still applies to them exactly as it does to locals: an admin must let them into the building first. Federation widens who can be invited; it never widens who gets in uninvited.