Self-host Logdash: status and how to run it locally

Logdash is MIT licensed and the repository is public. Running it in production on your own infrastructure is not supported yet. Here is what works and what does not.

The entire product lives in one public repository. There is no open-core split, no private mirror and no feature held back. You can read every line, fork it and run it on your own machine today.

What you cannot do today is run it in production without work we have not done for you. This page names that work rather than pretending it is not there.

What exists today

  • A backend image at apps/backend/Dockerfile, three stages on node 22.
  • A status page image at apps/status-page/Dockerfile.
  • MongoDB schema migrations through migrate-mongo, and ClickHouse migrations through clickhouse-migrations.
  • A docker-compose.dev.yml that brings up Mongo, Redis and ClickHouse for development.

What blocks production self-hosting

None of these is hypothetical. Each one is a thing you would hit within the first hour.

  • Stripe and Resend throw inside their constructors when their keys are empty, and both are built at boot, so the backend process will not start without them.
  • GitHub and Google OAuth are the only login methods. There is no email or password login, so a self-hosted instance cannot sign anyone in until you register your own OAuth apps.
  • Around 40 environment variables, most of them cloud-only.
  • No compose file that runs the applications. The one in the repository starts the datastores and nothing else.
  • No published container images. You build them yourself.

Run it locally today

A development instance on your own machine does work, and it is the same set of commands contributors use. From a clean checkout:

Running locally
pnpm install
docker compose -f docker-compose.dev.yml up -d --wait
cp apps/backend/.env.example apps/backend/.env
pnpm --filter backend migrate-up
pnpm --filter backend migrate-clickhouse

# in two terminals
pnpm dev:backend
pnpm dev:frontend

Stripe and Resend accept placeholder keys, because their constructors only check that a key is present rather than that it works. Signing in is the part you have to supply yourself: put your own GitHub or Google OAuth credentials in apps/backend/.env, or nothing will let you through the door.

FAQ

Can I self-host Logdash today?

For development, yes. The commands above give you a working instance on your own machine. For production, no. Stripe and Resend keys are required for the process to boot at all, OAuth apps are required before anyone can log in, and there is no compose file or published image that runs the applications rather than the datastores.

Is Logdash actually open source?

Yes. MIT licensed, one public repository, no enterprise edition holding the interesting parts back. The hosted cloud is the paid product; the code is not the thing being sold.

What is the plan for self-hosting?

Make the cloud-only integrations optional instead of required, add a login path that does not depend on an OAuth app you have to register, cut the environment surface down, and publish images with a compose file that runs them. There is no date. Follow the issue below rather than trusting this paragraph.