Cameron White, front page

Telcodash

(320) Specification from the portfolio of Cameron White.

Role Software Engineer
Period
November 2026 - May 2027
Repository
Telcodash/core
Languages
TypeScript 58 %, PHP 41 %, CSS 1.2 %
Created
17 Nov 2026; last push 18 Nov 2026

Abstract

A fully-featured management stack for a telecommunications provider featuring simulated customer/billing accounts, MSISDN/SIM management and team management with RBAC.

Figure 1: block diagram of the Telcodash stack A staff member's browser 321 reaches Core 322 over HTTPS. Core holds the web interface 323 and the application 324, which handles sign-in, teams and role-based access, and keeps its own data in a database 325. Core never calls a daemon directly: it posts tasks to the task gateway 326, which checks each one against its catalogue and queues it in Redis 327 with BullMQ, then posts signed webhooks back to Core as the task progresses. Each daemon 328 consumes its own queue and owns its own SQLite database: the customer daemon 328a, MSISDN daemon 328b, billing daemon 328c, subscription daemon 328d and usage daemon 328e. Billing publishes account events that the MSISDN daemon follows to bar and unbar numbers; the subscription daemon publishes line events that billing and usage both follow; and billing asks the usage daemon for usage totals on each daily run, all over Redis. DATABASE 325 QUEUES 327 DAEMONS 328 WEB INTERFACE React · Inertia 323 APPLICATION Laravel · RBAC 324 TASK GATEWAY Bun · TypeScript HTTP API · BullMQ customers SQLite 328a msisdn SQLite 328b billing SQLite 328c subscriptions SQLite 328d usage SQLite 328e HTTPS TASKS WEBHOOKS ACCOUNT EVENTS LINE EVENTS USAGE TOTALS 321 322 326 SQLite Redis jobs · streams Figure 1: block diagram of the Telcodash stack A staff member's browser 321 reaches Core 322 over HTTPS. Core holds the web interface 323 and the application 324, which handles sign-in, teams and role-based access, and keeps its own data in a database 325. Core never calls a daemon directly: it posts tasks to the task gateway 326, which checks each one against its catalogue and queues it in Redis 327 with BullMQ, then posts signed webhooks back to Core as the task progresses. Each daemon 328 consumes its own queue and owns its own SQLite database: the customer daemon 328a, MSISDN daemon 328b, billing daemon 328c, subscription daemon 328d and usage daemon 328e. Billing publishes account events that the MSISDN daemon follows to bar and unbar numbers; the subscription daemon publishes line events that billing and usage both follow; and billing asks the usage daemon for usage totals on each daily run, all over Redis. DATABASE 325 QUEUES 327 DAEMONS 328 WEB INTERFACE React · Inertia 323 APPLICATION Laravel · RBAC 324 TASK GATEWAY Bun · TypeScript HTTP API · BullMQ customers SQLite 328a msisdn SQLite 328b billing SQLite 328c subscriptions SQLite 328d usage SQLite 328e HTTPS TASKS WEBHOOKS ACCOUNT EVENTS LINE EVENTS LINE EVENTS USAGE TOTALS 321 322 326 SQLite Redis jobs · streams
FIG. 1 Block diagram of the Telcodash stack
  1. 321 user's browser
  2. 322 Core (staff application)
  3. 323 web interface
  4. 324 application, sign-in and RBAC
  5. 325 Core database
  6. 326 task gateway
  7. 327 Redis queues and event streams
  8. 328 daemons, each with its own queue and SQLite database
  9. 328a customer daemon
  10. 328b MSISDN daemon
  11. 328c billing daemon
  12. 328d subscription daemon
  13. 328e usage daemon

Brief description of the drawings

  1. FIG. 1 is a block diagram of the Telcodash stack, showing how Core, the task gateway and the daemons communicate.

Detailed description

For my dissertation project, I’m building Telcodash - an all-in-one management suite for a telco provider which features simulations for all types of consumer or business management.

The “core” houses essential data like employee login info and RBAC assignments to ensure users can interact with the right components at the right time. Functions hand off to the Queue, which is a distributed worker which takes a JSON payload from Core and routes it through to the appropriate “Daemon” (see diagram above.)

The project is open-source on GitHub and is still in continued development. It mainly features TypeScript with Bun frameworks, using SQLite for persistent memory and Redis for on-the-fly caching of results and information. All data transmission is done through private networking over encrypted tunnels and all elements of the stack are containerised and composed with Docker for distributed high-availability deployments on any machine.

References cited

  1. Telcodash/core TypeScript · created 17 Nov 2026
  2. camwhi-te/teledash-contracts Teledash message envelope, command/event and read-API JSON Schemas with generated TypeScript and PHP types. PHP · created 26 Oct 2026