Linkiny runs as a single Go binary. Managed deployments add a thin “managed middleware” that routes each subdomain to its own store for auth + identity, while sharing one DB for spaces, entries, and federation state.

Why: running 10,000 Postgres clusters for 10,000 users is absurd. Running one SQLite database in WAL mode with per-user namespacing is cheap, fast, and auditable.

Public endpoints (/markets/, /blogs/, /channels/) render per-subdomain by filtering space.created_by against the node’s owner UUID. Same code path, different tenant.

Federation isn’t a bolted-on “bridge” — it’s the same space model extending across nodes. Every space has a read_mode and write_mode; public-read spaces appear on /api/v1/federation/discover and get fanned out to peers for search and discovery.

Most messengers are hosted for you on a single corporate server. Your name, your contacts, your files — all inside someone else’s database.

Linkiny flips that: every user gets their own subdomain (e.g. alice.linkiny.com) that they own. Their chats, blog, marketplace listings, and files live under that subdomain. The app, the API, the public page — same URL.

You can host your own node. You can move. You can run Linkiny on a $5 VPS. You can federate with other nodes, share content, and talk to people on different servers without friction.

It’s email, but alive: realtime chat, voice, video, presence — federated, encrypted, ownable.

The rest of this section explains how we got here and where we’re going.

Shipped (Apr 2026)

• One-command self-host: VPS + domain, SSL auto-renew, Let’s Encrypt wired in
• Chat text + media in one message (no more ugly separate sends)
• Channel public broadcasting with federated media rendering
• Dating feed with cross-node photo resolution
• Market + Jobs aggregators across the federation
• iOS app with calling, channels, dating, market browser
• Web app parity and static public pages with federation discovery

Next

• Android app (2026 Q3)
• Group calls on SFU (partial TURN already shipped)
• Mail: full SMTP bridge so user@user.linkiny.com works with any client
• Space cover image polish (shipped Apr 2026)
• One-click “move my node”: export and import your whole universe between providers
• Open source release

Everyone’s rediscovering that putting everything on one megacorp server has downsides. Federation isn’t a magic cure — it shifts the incentive structure. When you host your own node the trade-offs between convenience, control, and community become yours to choose.

Linkiny’s federation is WhatsApp-simple at the surface. You add a contact by their domain. Messages deliver in real time. Blog posts and listings from your node appear on other peers’ Discover feeds if you made them public. Search spans the federation (cached with explicit TTLs).

Under the hood it’s boring: signed JSON POSTs between nodes, mutual TLS, retry queues. The interesting part is the product: one UX across self-hosted and managed, one identity across chat and blog, one code path across web and iOS.