SHADE

Sign-in, accounts, permissions, an admin, an HTTP API, an audit log and plugins, for the small business that runs it.

In development · pre-release Open source, self-hosted
  • TypeScript
  • Node
  • Hono
  • Nuxt 4
  • Drizzle
  • Postgres 18
  • Valkey
  • Docker
SHADE’s admin running locally with demo data, showing the audit log.
Close-up of a plugin package waiting for an admin’s approval.
  1. Plugins: untrusted ones run in a sandbox, trusted ones are signed and approved by an admin.
  2. The audit log: every change, and who made it.
The hard part

Running plugins safely: untrusted plugins run in a workerd sandbox, and trusted ones must be signed and approved by an admin. Anyone can sign and install plugins on their own host; there is no key only RG Digital holds.

01

The problem

I built SHADE because of dashboards and CMSs. Each serves its own purpose, and each tends to grow past it. A dashboard starts as an internal screen for managing things and ends up as the API all data runs through. A CMS starts as the backend of a website, gets a webshop attached, and at some point can’t keep up.

SHADE (Self-Hosted Adaptive Data Engine) is open source software that a small business runs its own systems on. It brings the parts every one of them needs: sign-in, accounts, permissions, an admin, an HTTP API, an audit log and plugins. Each project adds the plugins it needs and its own frontend.

Next to those it has connections to outside services, and tools for data security and privacy. On top of that you build plugins. A plugin asks for the capabilities it needs and holds only those, so it can’t do more than an admin allowed. You write only the logic your application needs, not a whole application.

02

Constraints

One instance per business: one Docker image with Postgres 18 and Valkey. Nothing is shared between businesses.

The business owns its instance outright, with no licence keys. Anyone may host it, run it and change it. It’s self-hosted. RG Digital built it, and you’re never tied to it. For help with SHADE itself, go to the project.

It’s pre-release and licensed Apache-2.0. The repositories go public at the first stable release.

03

Decisions and why

Postgres is the only database of record. Valkey holds only work in flight, so losing it loses no data.

Plugins come in two kinds. Untrusted plugins run in a workerd sandbox; trusted ones must be signed and approved by an admin. Anyone can sign and install plugins on their own host.

Every decision is written down as a decision record.

04

What broke

Nothing broke outright. The pressure came from building it together with AI: every function, and every connection between functions, had to be secure and stay readable. So SHADE is split into six layers (kernel, foundation, content, publishing, management and entry), each handling only what belongs at its level. Parts use only lower layers, and an architecture test refuses any import that breaks that map.

05

How it was built

Claude Code implements features end to end. I review every pull request, make the product decisions and record them as decision records.

Posts about SHADE

Let’s talk

About a project, or about a role on your team. You’ll hear from me within 24 hours.

— Dimitri, RG Digital

Email me to plan a call A reply within 24 hours · NL or EN