Company
The stack we run, and why each piece is in it
No single-framework story — the stack is chosen per problem across client work and NexBroad-Reach alike. Every line below is also named on the service page it belongs to.
By category
What's actually in the stack
The same facts as each service page, grouped by category instead of by discipline.
- Application & APIs
- Java · Spring Boot · Node.js · TypeScript · ExpressSpring Boot where the domain is heavy and long-lived; Node with TypeScript where the work is I/O-bound and one language across the stack is worth more than a second runtime. NexBroad-Reach's own API runs on the latter.
- Front end
- React · Next.js App Router · AngularNext.js when routing, metadata and first paint are server concerns; a plain React app when the product lives entirely behind a login; Angular where a team already runs it and consistency wins over novelty.
- Styling & motion
- Tailwind CSS · CSS custom properties · design tokens · Motion · GSAP · three.jsUtilities sit on top of a token layer, so a theme change is a variable, not a second set of rules. Motion libraries are used only where they carry meaning and kept inside their own components so the rest of the bundle doesn't pay for them.
- Mobile
- Kotlin · Android SDK · Jetpack · SQLiteNative where the app needs the platform properly — background execution, notification behaviour, hardware access — with a real on-device database, not a cache, so pending changes are rows a crash can't lose.
- Data & storage
- PostgreSQL · MySQL · MongoDB · DynamoDB · RedisPostgres is the default — a billing ledger wants transactions. MongoDB and DynamoDB appear where the shape is genuinely document- or key-oriented. Redis carries job queues and ephemeral state.
- AI & automation
- Provider APIs · retrieval pipelines · structured output · queues · scheduled jobs · webhooksModels are called as services behind our own interface, so a provider swap is a config change, not a rewrite — outputs are validated against a schema before they reach the product. Model calls are slow and occasionally fail, which makes them background jobs, never inline in a request a person is waiting on.
- Voice & messaging
- Text-to-speech · programmable voice · DTMF capture · Amazon SNS · SESCarrier-grade telephony rather than an app-to-app channel, so a call reaches a handset with no install and a keypad press comes back as data — this is what runs NexBroad-Reach's voice broadcasts. Fan-out and transactional mail run through managed services rather than a server nobody wants to own.
- Cloud & delivery
- AWS ECS · Fargate · Lambda · RDS · S3 · Docker · CI/CD · infrastructure as codeLong-running services on ECS with Fargate so there's no fleet to patch; Lambda for event-driven work idle most of the day. Environments are defined in files under review, so rebuilding one is a pipeline run, not an archaeology project.
Tell us what you want built
A short brief is enough to start — what you're trying to do, and roughly for whom.