┌──┐
│  │
└──┘

· · ·
 · ·
· · ·

│
├─
│
└─

┌─┐
└─┘

┌── . ──┐
│       │
└───────┘

·
│
·

┌┐
││
└┘

· ·
 ·
· ·

└──┘
  ·

·

┌┐
└┘

│ · │

┌─┐ ·

· └──┘

┌─ .stbl ────────┐
│ hidden · load  │
│ bearing · always│
└────────────────┘

┌ status ──┐
│ ok       │
│ always   │
└──────────┘

we build the bottom layer. you don't see it until you look.

// thesis

.stbl is a small studio building open-source infrastructure software for teams that want cloud-like ergonomics without giving up control. Each product lives in its own repo with its own community. The .stbl layer underneath — build tools, design language, engineering bar — is constant.

§ 01 — principles

five tenets.
load-bearing.

→ I

open source by default

Every product we ship is MIT code, OFL fonts, CC BY assets. We don't have a "commercial" fork hiding behind a feature flag. If it's not open, it's not us.

→ II

control without ceremony

Self-hosted should not mean babysitting YAML at 3am. Cloud ergonomics — sane defaults, one-command deploys, batteries included — on infrastructure you actually own.

→ III

the boring layer is the layer we ship

Build tools. Design language. Engineering bar. The stuff you'd otherwise write for the fifth time, then abandon. We write it once, maintain it, give it away.

→ IV

one studio, many products

Each product lives in its own repo, with its own community, its own release cadence. The .stbl layer underneath stays constant. The brand stays constant. The bar stays constant.

→ V

hidden by design

In Unix, anything starting with a dot is invisible by default. ls won't show it. ls -la will. That's our relationship to our products — always present, often unseen, load-bearing.

§ 02 — catalogue

seven products.
one layer.

001

anlytraby .stbl

Crypto analytics & auto-trading platform for algo traders. Aggregates 17 exchanges into one terminal. Backtest, deploy, monitor — all on your own keys.

private beta
app · trading

landing →
app ↗
github →

002

plexorby .stbl

Self-hosted cloud platform. Run workloads on your own metal with cloud ergonomics. Compute abstraction, runtime providers (k3s / docker / podman), cluster orchestration.

alpha
infra · platform

github →

003

re.passwordby .stbl

Self-hosted password manager. End-to-end encrypted. No subscriptions, no clouds you don't own. Your secrets, your hardware.

alpha
app · security

github →

004

notifliwyby .stbl

Distributed notification bus for .NET apps. Channels for Telegram, MAX, email, webhooks. Reliable delivery, retries, templated payloads.

live
library · net

github →

005

cyclexby .stbl

Distributed task scheduler for .NET. Cron, intervals, one-shot jobs. Backed by your database — no Redis, no separate service to run.

alpha
library · net

github →

006

synaptix.packagesby .stbl

Shared .NET primitives used across stbl products. Result types, identifiers, pagination, validation — the boring load-bearing code, written once.

live
library · net

github →

007

kubixby .stbl

To be defined. Slot reserved, repo parked. Sometimes the best move is to hold a name until the right product grows into it.

tbd
infra · parked

github →

—

brandmeta

The .stbl brand book itself. Mark, wordmark, lockup pattern, design rules, asset hierarchy. Every product inherits from this.

live
meta · design

github →

// § 03 — etymology

why .stbl?

The name predates the org. It was a directory name first — .stbl/ — sitting in someone's home folder, holding build scripts, design tokens, the boring layer underneath everything else.

When it came time to name the studio, no other word fit. .stbl already described the relationship: always present, often unseen, load-bearing. The dot was added deliberately. In Unix, anything starting with a dot is invisible by default.

$ ls -a ~ .stbl/ $ cd .stbl && ls brand/ build/ deps/ docs/ templates/ $

we build the bottom layer. you don't see it until you look.

five tenets.load-bearing.

seven products.one layer.

why .stbl?

building something?

five tenets.
load-bearing.

seven products.
one layer.