Technology
The stack, pipeline and standards behind every Nexum Forge build: Next.js and TypeScript, composable commerce, Kubernetes and Terraform, OpenTelemetry, and a performance gate that fails the build.
Technology
Boring where it matters, modern where it pays
We pick technology the way you would pick a supplier: on total cost, on how easy it is to hire for, and on how it behaves at three in the morning. Novelty is a cost, not a feature.
- Every dependency has an owner, a support horizon and an exit plan
- Infrastructure defined as code, in your cloud account, reproducible from an empty region
- Every environment created by the same pipeline, so staging is not a hand built snowflake
- Security scanning, dependency auditing and secret detection run on every commit
- Observability designed with the system, covering business metrics as well as infrastructure
Pipeline
From commit to production
Continuous delivery pipeline and environment promotion
Figure 11 / delivery pipelineFigure 11. The performance gate is not advisory. A change that pushes largest contentful paint or bundle size past the agreed budget fails the build.
Stack
What we build with
This is what we use most. It is not a rule. If your team already runs Java and Azure well, we will build you something excellent in Java on Azure.
| Layer | Primary | Also works with |
|---|---|---|
| Storefront | Next.js, React, TypeScript | Nuxt, Remix, Astro, SvelteKit |
| Styling and design system | Tailwind, CSS modules, Storybook | Vanilla Extract, Panda, Stitches |
| Commerce engine | commercetools, Shopify Plus | Adobe Commerce, Spryker, Medusa, custom services |
| Services | TypeScript on Node, Go | .NET, Java, Python |
| Data | PostgreSQL, Redis, Kafka | MySQL, DynamoDB, RabbitMQ, SQS and SNS |
| Search | Algolia, Elasticsearch | Typesense, OpenSearch, Constructor |
| Content | Contentful, Storyblok | Sanity, Strapi, WordPress headless |
| Cloud and runtime | AWS, Kubernetes, Terraform | Google Cloud, Azure, Vercel, ECS and Fargate |
| Observability | OpenTelemetry, Grafana, Datadog | New Relic, Sentry, Elastic |
| Testing | Vitest, Playwright, k6, Pact | Jest, Cypress, Gatling, Selenium |
Table 11. Selenium and Cypress appear here because plenty of clients already own large suites in them, and rewriting a working regression pack is rarely the best use of a budget.
Security and quality
The standards that apply to every project
01
Secure by default
- Dependency and container scanning on every build
- Secret detection before a commit can land
- Least privilege roles, short lived credentials
- Annual penetration test, findings tracked to closure
02
Quality engineering
- Test pyramid with fast unit coverage at the base
- Contract tests between every service pair
- Playwright journeys for revenue critical paths
- Visual regression on the design system
03
Data protection
- GDPR data map maintained with the build
- Personal data minimised and encrypted at rest
- Deletion and export handled through a documented process
- Card data never touches your systems
Next step
Tell us what is slowing your commerce platform down
Send the brief. A principal architect reads it, then you get a written technical assessment with options, effort and risk inside five working days. No sales call required first.