GeeleemA community is a place
Each community is its own home: members, apps, house rules, and a public face. It can live at a Geeleem address or on a domain you already own. What happens in one community does not spill into another.
Home / Platform
Platform
Little machinery. A lot of house sense.
This page is the short version of how Geeleem is put together — the kind of thing a host or a partner asks before they trust a community to it. No internals. No diagrams of plumbing.
Apps you switch on
You do not buy a monolith and hide half of it. You install what this community needs — bookings, events, a shop, support — and add more later without pretending you are migrating to a new product. New community apps can be added without rebuilding the house.
Two kinds of permission
Access is the right to enter. Membership is a deeper seat — purchased or earned. Together they decide who may book, who may buy, and which tools even appear. People should not trip over keys they were never meant to hold.
Quotas for real sharing
Room hours, credits, and usage limits can belong to a person or to a team. Members who sit in more than one team can choose which pot to spend. That is how studios and companies actually behave.
A family of places
Sub-communities — a floor, a city, a programme — keep their own life while still recognising people from the parent. Useful when you are larger than one door and smaller than a corporation.
Languages of the room
Persian and English are first-class. Right-to-left is not an afterthought. An assistant can help members in the language they already use. Telegram is there when the community already lives in a chat.
What we do not publish
This site will not teach anyone how the engine is built
If you are looking for schemas, internals, or a developer cookbook, you will not find them here. This is a front door for people who run communities and businesses inside them.
Curious how it would sit on your domain?
Request a walkthrough. Bring the name of the community and the week you actually live.