Frontend
- React, Next.js, TypeScript
- Vue and vanilla where it fits
- Design systems and accessibility
- Progressive web applications
Technology
The stack and standards we build on
We favour mature, well-supported technology you can hire for. Novelty is only worth it when it solves a problem the boring option cannot.
Capabilities
What we work with day to day
Backend
- Node.js, Python, Java, .NET
- REST and GraphQL APIs
- Event-driven and queue-based systems
- Domain-driven design where it earns its keep
Data
- PostgreSQL, SQL Server, MongoDB
- Warehousing and ELT pipelines
- Reporting and BI tooling
- Governance and access control
Cloud
- AWS, Azure, Google Cloud
- Containers and Kubernetes
- Serverless where it reduces cost
- Terraform and infrastructure as code
Delivery
- Git-based workflows and code review
- CI/CD with automated gates
- Automated testing at multiple levels
- Environment parity from dev to production
Security & ops
- SSO, RBAC, and secrets management
- Logging, metrics, and alerting
- Backup and tested recovery
- Dependency and patch management
TODO: trim to the technologies Crozent actually staffs and supports.
Standards
How we decide what to use
Technology choices are documented with the reasoning behind them, so the next engineer understands why — and can revisit it when circumstances change.
- Prefer technology with a long support horizon and a real hiring pool
- Every significant decision recorded as a short architecture decision record
- No proprietary runtime the client cannot maintain without us
- Security and observability designed in, never retrofitted
- Infrastructure reproducible from code, in your accounts
Architecture decision recordsEvery project
Automated test coverageEnforced in CI
Secrets outside the repositoryAlways
Monitoring before launchNon-negotiable
Wondering if your stack is the right one?
An architecture review gives you an independent read before you commit to the next phase.