Sign In

Documentation · Blue Notes

One page. The whole control plane.

Integrate with the DEML user control plane, then hand sealed work to FORJD. Interactive sandbox: Swagger UI.

API REFERENCE

Documentation

Authenticate once, then call DEML for identity and learning surfaces. Sealed ingest and processing run in FORJD through the mapped tenant credential.

Authentication

Browser sessions use Firebase Auth through Django. Headless integrations use a deml_… API key as Bearer or X-API-Key. Keys are shown once at creation and hashed with SHA-256 at rest.

HTTP Header
Authorization: Bearer deml_YOUR_API_KEY

Sealed FORJD handoff

Batch sealed envelopes into FORJD. DEML never stores ciphertext or end-user tokens on the upstream call.

POST /api/v1/forjd/ingest

Contract probe

Confirm the DEML ↔ FORJD contract version and readiness before cutting traffic.

GET /api/v1/forjd/capabilities

Interactive reference

Browse every operation, authorize with your token, and execute calls in the browser.

Open Swagger UI

Integration guides

First-class guides for Kubernetes, TensorFlow, PyTorch, Apache Spark, Databricks, and AWS Redshift live in the developer portal.

Open developer portal
FIELD LOG · BLUE NOTES

Engineering, in the open

The operating record behind the platform — releases, architecture decisions, and reliability work. Newest dispatches first.

FORJD is the data plane

DEML owns identity, billing, consent, and learning UI. Sealed ingest, projections, analytics, replay/DLQ, SIEM/SOAR, and ML execute exclusively in FORJD via tenant-bound fjsvc_ credentials. The Django BFF never forwards Firebase tokens upstream.

Pro entitlements

Stripe-backed Pro gates premium BFF writes (exports, SIEM, projections run, playbooks). Standard keeps core read/ingest/status/report paths.

Full archive

Browse every Blue Notes dispatch on the marketing site, or follow the RSS feed.

Browse archive RSS