One throwaway machine running the entire Siraj platform — the Arabic-first professional work assistant — with every plane the repository defines: the product, its operator console, the observability plane, product analytics and the backing services. Seeded with full-coverage showcase data in Arabic and English.
The member web app: chat, projects, library, law corpus, tasks, reports, artifacts, the Word-class editor.
https://demo-siraj.signit.sanoura@demo.siraj.sa (owner) · khalid@… (admin) · abdullah@… (custom role) · sara@… · reem@…maha@showcase.siraj.sa — the richest demo view — a full year of usage: sessions, approvals, law-corpus Q&A, projects, reports and live insight charts · faisal@… — 4 sessions · omar@… — 3 · lina@… — org owner (and the console operator) · rania@…, tariq@… — member/corner-case personasThe platform-operator plane: organizations, plans, models and routing chains, abuse posture, audit.
https://console.demo-siraj.signit.saThe same API the apps ride; interactive docs are enabled on this demo.
https://demo-siraj.signit.sa/api/v1/docsThe ops plane (Grafana + Prometheus + Loki + Tempo). Dashboard «Siraj overview» plus RED metrics; full request traces from the api and the worker land in Tempo.
https://grafana.demo-siraj.signit.saThe embedded Prometheus behind Grafana: scrape targets, alert rules, raw query API. Both targets (siraj-api, siraj-worker) are up.
https://prometheus.demo-siraj.signit.saWhat every model run did: prompts, completions, tool calls, tokens, cost, scores, datasets. Traces arrive over OTLP as siraj.run.
The Sentry-compatible error tracker. Three projects: Siraj backend (api + worker), Siraj web app and Siraj admin console (browser bundles).
https://errors.demo-siraj.signit.saActivation, retention, feature adoption, active people, power users, segments, platforms and clients, run quality — over the behavioural events the product emits.
https://analytics.demo-siraj.signit.saThe column store behind Metabase and Langfuse. Database siraj_analytics holds the product events (~117k seeded) and rollups; the web UI is at /play.
Realm siraj with the siraj-api OIDC client, imported from the repo. Inspectable, but this demo signs users in through the dev adapter, so Keycloak is not on the login path.
S3 for uploads, artifacts and exports; presigned URLs resolve against the storage host. The console browses buckets.
https://s3-console.demo-siraj.signit.saEvery email the platform (and GlitchTip) sends — verification, notifications, digests — lands here.
https://mail.demo-siraj.signit.saThe shared Postgres, preregistered: databases siraj (the product, with pgvector), langfuse, glitchtip, metabase.
The metasearch engine behind the assistant's web-search tool. Configured as an API: JSON results only, the HTML result page is off by design.
https://search.demo-siraj.signit.sa/search?q=…&format=jsonBAAI/bge-m3 on CPU — the multilingual embeddings behind semantic search, the library and message recall.
https://embeddings.demo-siraj.signit.sa/docsSlack, Jira, Confluence, Notion, ServiceNow, GitHub, GitLab, Linear, Google, Microsoft Graph, an MCP server, OIDC, payments (Moyasar, Stripe), SMS and OpenAI — with real auth semantics and in-memory state, for connector demos without vendor accounts.
https://mock.demo-siraj.signit.sa/healthRunning, reachable from the other services but with no public name: Postgres 17 + pgvector (browse it through pgAdmin), Redis ×2 (app cache; Langfuse/GlitchTip queues), ClamAV (upload scanning), the worker (jobs, runs, schedules — its traces and metrics show in Grafana).