Stack and standards

Technology and engineering standards

Frontend in React and Next.js, backend in Node.js, Python or PHP, depending on the task and your team. Data in PostgreSQL, infrastructure in Docker with CI/CD.

Infrastructure Docker · CI/CD · Sentry Data and jobs PostgreSQL · Prisma · Redis Backend Node.js · Python · PHP Interface Next.js · React · Tailwind
production · healthy
Our stack
TSTypeScriptReReactNNext.jsTwTailwind CSSNoNode.jsNeNestJSPyPythonphpPHPPgPostgreSQLPrPrismaRdRedisBqBullMQAILLM APIsPwPlaywrightTgTelegram APIDkDockerGAGitHub ActionsNxNginxSeSentryViVitestTSTypeScriptReReactNNext.jsTwTailwind CSSNoNode.jsNeNestJSPyPythonphpPHPPgPostgreSQLPrPrismaRdRedisBqBullMQAILLM APIsPwPlaywrightTgTelegram APIDkDockerGAGitHub ActionsNxNginxSeSentryViVitest
Architecture

How a typical system is built

A user request passes through the same layers in a website, an online shop or a portal.

UsersNginx · CDNNext.jsAPI · Node · Python · PHPPostgreSQLRedis · BullMQLLM · AISentry · Monitoring
Backend

Node.js, Python or PHP: how we choose

We choose the language for the task and for the team that will maintain the system.

NoNode.jsNode.js · NestJS
When we choose it
  • Web platforms and SaaS
  • One TypeScript codebase with the frontend
  • Real time, queues, integrations
PyPythonPython
When we choose it
  • AI and data processing
  • Automation and scraping
  • Libraries for analytics and ML
phpPHPPHP
When we choose it
  • Websites and online shops
  • Improving existing PHP projects
  • Simple, widely available hosting
Technology

Our stack, as it looks in the code

import { getOrders } from "@/lib/api";import { OrdersTable } from "@/components/orders-table";// Server component: data arrives with the first paintexport default async function OrdersPage() {  const orders = await getOrders({ status: "open" });  return (    <section className="grid gap-6 p-8">      <h1 className="text-2xl font-semibold">Orders</h1>      <OrdersTable rows={orders} />    </section>  );}
app/[locale]/orders/page.tsx✓ build · 1.2 s · 0 type errors
CI/CD

Every change's path to production

No change reaches users without checks.

  1. Commit
  2. Lint and types
  3. Tests
  4. Build
  5. Staging
  6. Production
  7. Monitoring
Standards

How we write code

The same standards for a landing page, an online shop and a web portal.

Types and review

Strict TypeScript, and a second developer reviews every change.

Automated tests

Unit and integration tests run on every commit.

CI/CD

Build, checks and deployment are automated; rollback in minutes.

Monitoring

Errors and performance visible in Sentry and metrics from day one.

Security

Access control, encryption, backups and dependency updates.

Documentation and handover

Code, infrastructure and decisions documented so that your team can carry on.

Technology for fast, secure and search-friendly websites

The choice of technology decides how fast a website loads, how well search engines read it and how long it can keep evolving. Our main stack is TypeScript with React and Next.js: pages are pre-rendered on the server, load fast and are fully readable for Google and AI crawlers.

On the backend we use Node.js, Python or PHP: Python mainly for AI and data processing, PHP for websites and shops your team already knows. Data lives in PostgreSQL, background jobs run on Redis queues, and everything ships in Docker containers with CI/CD.

Every change goes through automated tests, code review and a staging system before it goes live. Monitoring reports errors before your customers notice them.