Devign internal tools

Problem

Running eight products means running the machinery behind them: monitors, recruitment, support tickets, boosts, the books. Off-the-shelf tools were either priced per seat or did not fit how the team actually works, so we built our own.

None of these are products. They are listed here because they are part of how we run what we build — and because the same stacks and habits go into client systems.

What we built

• JARVIS — the control panel and content-intelligence dashboard for the studio. Next.js 16, React 19; Docker and pm2. Own page.
• Devign Ops — fleet monitoring and alerting: uptime monitors, fleet scripts, automations, alert channels and Sentinel, with Grafana and ntfy links. PHP, inside the agency back end.
• Devign Boost — LIVE and video boost management for Devign agencies and account managers; agencies sign in with credentials from their manager. Next.js, English and Arabic.
• BetterChat — a three-column, WhatsApp-style agent inbox for creator recruitment: contact enrichment and recruitment-stage sync per market, single sign-on with the agency back end. Custom PHP.
• Support desk — a ticket portal with team, notifications and admin views; alerts go out through ntfy and Discord. Custom PHP.
• Devign Taxes — accounting and financial management for the firm: clients, expenses, accounts, firm settings and an assistant module. Next.js 16 / React 19 front end, Django back end.
• TCN Agent Ops — the operations console behind TCN Agent. Vite single-page app.
• Devign Apps — an unreleased comparison and pricing site for Agency Suite and TCN Agent, behind basic auth until launch. Next.js static export.

Outcome

• All eight are login-walled or unreleased; there is no sign-up and no pricing, and we publish no usage figures for them.
• Each runs on the same hosting and with the same discipline as the public products — JARVIS watches the rest.

Verifiable facts only — no estimates.