StackSmith

Self-hosted deployment kits — pinned Docker Compose stacks with runbooks and documentation for popular open-source services. Eight kits,...
Location hidden
•Created byProfile pictureAditya Kumar
2 joined
Home
ProductsReviews
Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

Roadmap — what we are working on

Current state and what is next.


DONE


  • eight kits, five tiers each

  • the full source browser, so you can read every file before buying

  • component guides for every service in every kit

  • instant delivery: payment, then a download link by email


NEXT


  • more components in the data and local-AI kits

  • a short video walkthrough of the first deploy

  • upgrade notes when a pinned component moves


WANT SOMETHING?


Post it here. Requests from people who bought a kit shape what gets built

next.

Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

Requirements and expectations

So nobody is surprised after buying.


YOU SHOULD BE COMFORTABLE WITH


  • a command line

  • editing a config file

  • running docker compose up and reading the output


YOU DO NOT NEED


  • to write code

  • prior Docker experience — the runbook covers the operations

  • a specific provider — any VPS or server with Docker works


WHAT WE DO NOT DO


  • host anything for you

  • manage your server

  • guarantee a third-party project's behaviour


Support is by email and here in the community. Every purchase includes it.

The Scale and Complete tiers add 30 days of priority support; Complete

includes a live onboarding session.

Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

Which kit should I start with?

Short version: pick the one closest to something you already rent.


Replacing four or five SaaS tools for a product team → Hearth

Monitoring that costs more as you grow → Beacon

Team docs, tasks and chat on someone else's servers → Lodestar

Analytics on a metered warehouse → Quarry

A public edge you want hardened → Rampart

Designing and testing APIs → Meridian

Running your own CI instead of paying per minute → Anvil

Local models without sending data out → Atlas


Every kit comes in five tiers. Starter is two or three services. The top

tier is the complete deployment with a live onboarding session.


Not sure? Post here with what you run today and we will point you at the

right one.

Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

Licensing — what you may and may not do

Straight answer, because people ask.


WHAT YOU GET


A licence to use and modify the kit on your own infrastructure. Yours, or

your company's.


WHAT YOU MAY NOT DO


Resell or redistribute the kit itself as your own product.


THE COMPONENTS


Every bundled project keeps its own licence — MIT, Apache-2.0 or

BSD-3-Clause — and its own copyright. We do not relicense them. The full

list, with pinned commits and upstream links, is on the licensing page:



If you redistribute a stack, keep each project's copyright and licence

notice. ATTRIBUTION.md inside every archive lists them.

Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

Why the components are pinned

Every kit fetches its upstream projects at an exact commit, not a branch.


Upstream projects move. A latest tag that works today can break your stack

next month — a config format changes, a port moves, a dependency is dropped.


Pinning means your deployment keeps working. When you do want to move, you

change the commit deliberately and read the release notes first.


The fetch script is the only thing that touches upstream source. We do not

vendor other people's code into the archive. You get the integration layer —

compose files, environment template, runbook, guides — and the script that

pulls the rest from each project's own repository.

Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

What's inside a kit

People ask what they actually get. Here is the exact file list for the

Hearth complete tier:


README.md what this is and the quickstart

docker-compose.yml starts every service in the tier

.env.example the settings you need to change

RUNBOOK.md daily checks, backups, upgrades, troubleshooting

verify.sh health check across the services

fetch-sources.sh pulls each upstream project at pinned commits

ATTRIBUTION.md every component, its licence and exact commit

docs/<component>.md one written guide per component


Three commands from download to running:


./fetch-sources.sh ./sources

cp .env.example .env

docker compose up -d && ./verify.sh


Requirements: Docker Engine 24+ with the Compose v2 plugin. Around 4 GB RAM

for light tiers, 16 GB+ for a complete deployment.

Profile picture
Aditya KumarProfile picture@businessmanaditya·Oct 19

Welcome to StackSmith

Welcome. This is the community for StackSmith — self-hosted deployment

kits.


WHAT WE SELL


Eight kits, each wiring well-known open-source services into a working Docker

Compose deployment:


Hearth application platform — backend, git, CI, CMS, commerce

Beacon observability — metrics, logs, traces, status pages

Lodestar private workspace — notes, tasks, files, diagrams, chat

Quarry data — collection, pipelines, warehouse, BI

Rampart edge — reverse proxy, TLS, WAF, hardening

Meridian APIs — design, mock, validate, gateway

Anvil developer platform — forge, CI, secret and IaC scanning

Atlas local AI — model runners, vector stores, RAG


Each kit ships a docker-compose.yml, an .env.example template, a RUNBOOK.md,

a verify.sh health check, a fetch-sources.sh that pins upstream commits, an

ATTRIBUTION.md listing every licence, and a written guide for every component.


Nothing is hosted. You run it on your own server.


Read the source before you buy — the whole file tree is public: