SOC_STATUS GREENUPTIME 99.998%MTTR 00:04:12EVENTS/DAY 14.2MCAPE_TOWN · UTC+2THEME
SHEL infosec
SHEL/infosec
./get-protection ◢./login
THEME
~ / work / silent-edge
02LIVE

Silent Edge

Cybersecurity · multi-tenant SOC platform

Our own security operations platform: a multi-tenant SOC console with tenant isolation enforced inside the database rather than the interface, live threat intelligence, and a client portal. Built because the firms that most need a 24/7 SOC are exactly the ones that cannot staff one.

Tenant isolation
Database-level
Access model
4-tier
Intel sources
MITRE · KEV · NVD
01

The firms that need a SOC most cannot staff one

A security operations centre needs analysts on shift around the clock, a SIEM, threat intelligence, and someone who knows what to do at 03:00. That is a headcount problem before it is a software problem, and it puts real detection out of reach for small and mid-sized firms — who are targeted precisely because they are assumed to be undefended.

02

One console, many tenants

Silent Edge is a multi-tenant console where our analysts work across every client while each client sees only their own estate. Staff get the operations view — alerts, devices, threat intelligence, incident playbooks. Clients get a read-only portal scoped to their organisation. Access runs on a four-tier model, from owner-level command down to org-scoped analysts and read-only client accounts.

03

Isolation belongs in the database, not the interface

The hard part of multi-tenancy is not building the screens — it is guaranteeing that one tenant can never reach another's data, including when the application layer has a bug. Separation is enforced with row-level security policies in PostgreSQL, so it holds at the data layer regardless of what the interface does. A query that should return nothing returns nothing, even if the code asking is wrong.

  1. Authenticated requestSession carries the user's organisation and role
  2. Row-level securityPostgreSQL policies scope every table to the caller's org
  3. Role gateMiddleware enforces route access per tier
  4. Scoped responseOnly rows the tenant owns are ever returned
Every request is scoped at the data layer. The application cannot opt out of the policy.
04

Intelligence that arrives before the incident

The platform ingests MITRE ATT&CK technique data, the CISA Known Exploited Vulnerabilities catalogue and NVD CVE records, and correlates indicators of compromise against telemetry from endpoint and RMM integrations. An AI specialist layer runs retrieval over an internal knowledge base, so analysts get grounded answers with sources rather than a plausible-sounding guess.

05

Running in production

Silent Edge runs on our own infrastructure behind nginx, containerised, serving both the client console and this site from the same platform. It is the system our analysts use daily — which means every rough edge is one we feel first.

Built with
NEXT.JS 15TYPESCRIPTSUPABASEPOSTGRESQLPGVECTORROW-LEVEL SECURITYDENO EDGE FUNCTIONSDOCKERNGINXCLAUDETURBOREPO

Build the
next one with us.

./start-a-project ◢