self-host-stack
self-host-stack/context-v/
36 files here
specs/4
Homebase MCP — one connector per client, every tool behind it
A client adds one address to Claude and their agent can move across CRM, wiki, data room, and post planner in a single task — because one plane fronts them all, authenticates them through didi.sh, holds the credentials, and serves our skills as both prompts and resources.
Per-Client Stack Deployment — Twenty First (reach-edu, then palmer-ai)
Stand up Twenty CRM for reach-edu, then palmer-ai, on Railway project-per-client — phase by phase, with a verification gate at every step.
Papermark Self-Hosted Dataroom Deployment
Complete deployment specification for self-hosting Papermark as an open-source virtual data room for sharing investment memos, pitch decks, and due diligence documents.
self-host-stack/specs
plans/1
reminders/4
Submodules detach because .gitmodules never said which branch
The parent pins a raw SHA, so every submodule update lands on a detached HEAD. Declaring branch and update in .gitmodules fixes it once for every clone — but the bulk scripts that promise to fix it are exactly the things that have historically detached submodules AND clobbered their remotes.
Creating a Railway service fires a build before you can configure it
The build that starts the instant a service is created runs with no domain, no variables, and the Dockerfile's ARG defaults. Read anything from it and you will draw the wrong conclusion about what Railway does and does not pass to a build.
railway config pull does not pin database images — read the plan
A pulled Railway IaC config re-declares every postgres() and redis() at the helper's default version. Applying it unchanged proposes a major-version upgrade on live databases.
self-host-stack/reminders
agent-skills/10
self-host-stack/agent-skills/custom-domain-cutover/skill
Point a custom (sub)domain at a Railway service and survive the cutover — DNS records, wildcard overrides, cert issuance, and the stale-cache theater that follows. Use whenever minting a `*.didi.sh` (or any custom) domain for a client hub/app, whenever a freshly-cut domain "doesn't work" on someone's machine while probes say it's live, or whenever the user says "I can't see the subdomain."
self-host-stack/agent-skills/decilehub-interface/readme
self-host-stack/agent-skills/decilehub-interface/references/connector-setup
self-host-stack/agent-skills/decilehub-interface/references/pipeline-vocabulary
self-host-stack/agent-skills/decilehub-interface/references/tool-map
self-host-stack/agent-skills/decilehub-interface/skill
Operate a VC firm's Decile Hub from Claude Desktop, claude.ai, or Claude Teams via Decile's native MCP connector — 158 tools across the LP/investor pipeline, deal flow, portfolio, fund admin, data room, and outbound email. Use when someone asks about an LP or a deal ("is X in our pipeline?", "what stage?", "who referred us?"), wants a call or voice memo logged, wants records created or updated, wants a pipeline or portfolio roundup, or wants to send an email, newsletter, PACT, or LPA. Supplies the safety tiering Decile omits (its 158 tools carry zero annotations, so list_people and publish_newsletter look alike), the People-vs-Organizations-vs-Prospects model, where notes actually land, the never-create-a-duplicate rule (there is no merge tool), and the discipline of reporting only what the record supports.
self-host-stack/agent-skills/decilehub-interface/templates/deal-upsert
self-host-stack/agent-skills/decilehub-interface/templates/lp-upsert
self-host-stack/agent-skills/decilehub-interface/templates/speech-to-text-upsert
self-host-stack/agent-skills/vc-firm-profile-ingest/skill
Research a VC firm from the open web and land it in BOTH systems in one pass — a Twenty CRM company record with a research note attached, and a cross-linked Outline wiki page in the Venture Firms collection following the house profile template. Use whenever the operator says "create a VC profile", "add <firm> to the CRM and the wiki", "profile <firm>", "research this fund and write it up", "who are they and should we care", or names this skill. Encodes the dedupe-first discipline (98+ companies already exist — never create a second record), the two-call note attachment Twenty requires, the composite link-field shapes that silently fail as plain strings, the Twenty↔Outline join (the wiki page header carries the CRM record UUID), the house page template with its open-questions checklist, and the sourcing hierarchy that keeps contaminated aggregator data out of the record. Client-scoped: collection and workspace IDs below are Palmer AI's.
explorations/9
Watchlist — Interesting Tools Not Yet Sorted
A running catch-all for tools worth a second look, before we know whether they map to a self-host-stack category, a personal-workstation list, or nothing at all.
Aggregating Historical Calendar Items for Lossless Twenty
Started as 'should we deploy cal.diy' and ended somewhere else entirely — cal.diy deletes the past by design, Twenty's importer already backfills everything, and the thing actually worth building is a one-time ICS backfill that never touches OAuth.
Do we need a sandbox behind homebase?
Homebase federates tools but stores nothing and runs nothing. The missing piece turns out to be two pieces — storage, which is already funded, and compute, which can wait.
Replacing Granola with an Open-Source Transcription Stack
Transcription is solved and free. Knowing who was speaking is neither — and it's the half that makes a meeting-notes product feel good.
Per-Client Self-Host Stacks, Twenty-First, on Railway
One playbook, three tiers: managed client stacks on Railway, a hub page clients actually use, and a per-client remote MCP server that could grow into a full context plane.
Should Hermes Agent Co-Locate on the Same Host as TwentyCRM?
Colocation feels like it should mean 'automatic access' — the evidence says it doesn't, and the real value is elsewhere.
Sharing One Hermes Agent Instance Across a 3-Person Client Team
Hermes Agent has no shipped multi-user mode — the gap is real, catalogued, and still open upstream.
An Instantly-Synced Shared Folder for a 3-Person Team
Nextcloud was the first name that came to mind — but the actual ask is pure instant file sync, and that's a different tool's specialty.
self-host-stack/explorations
issues/4
Postiz is the heaviest thing we run
Postiz and its dependencies account for more than half the memory in the client projects that have it — and memory is 93% of the Railway bill. Nobody is visibly getting value back.
Normalize Paths Everywhere — one URL shape for every client + service
Today every tool lives at a raw Railway hostname; the goal is one owned, legible shape — lossless.at/<client>/<service>/… — for humans and agents alike.
Which domain hosts what — lossless.at vs didi.sh
Client-facing apps have landed on both domains by accident of chronology, not decision. Nothing is broken; the next deploy will guess, and guess differently than the last one.
self-host-stack/issues