Skip to content
comark

Technology

A stack chosen for the long run.

Proven, well-supported technology that we know deeply, picked per project for what it has to do, and kept current for years after launch.

stack / comark
  1. 01Frontend

    Next.js · React

  2. 02Backend

    Node.js · NestJS · PHP

  3. 03Data

    MySQL · PostgreSQL · Supabase · Redis

  4. 04Infrastructure

    Linux · Nginx · Cloudflare · Bunny CDN

Alongside every layer

  • AI
  • Integrations

The stack, layer by layer

What each piece is for.

Four layers, from what users see down to the servers, with AI and integrations running alongside every layer rather than stacked on top.

FrontendWhat users see and touch
  • Next.js

    Websites and portals rendered on the server: fast, and readable by search engines.

  • React

    Interactive dashboards, CRM screens and admin consoles.

BackendBusiness logic and APIs
  • Node.js · NestJS

    APIs, webhooks, real-time features and background workers.

  • PHP

    Proven business systems, supplier APIs and extending existing platforms.

DataWhere records live and how fast they return
  • MySQL

    Transactional data for news sites, stores and business systems.

  • PostgreSQL · Supabase

    Complex queries, reporting and structured data, including Supabase projects.

  • Redis

    Caching, sessions and queues.

InfrastructureWhere it runs and how it is protected
  • Linux

    The server OS for everything we host and operate.

  • Nginx

    Web server and reverse proxy.

  • Cloudflare

    DNS, CDN, WAF and SSL in front of the sites we host.

  • Bunny CDN

    Image and media delivery for content-heavy sites.

05 · AI

Language models called from any layer through one governed AI layer, with permissions and logging.

  • Drafting and summaries

    Replies, notes and long threads condensed for a person to check.

  • Search and extraction

    Answers and fields pulled from your own documents and records.

AI solutions

06 · Integrations

External platforms connected over their official APIs.

  • Meta Graph API

    WhatsApp, Instagram and Messenger: the base of Engage.

  • Google APIs

    Analytics, Search Console and Maps.

Full catalogue below

How we choose

Boring where it should be. Modern where it counts.

Every technology decision is made against five questions, and written down in the project's architecture notes so the next engineer knows why.

  1. Longevity

    Will it still be maintained in five years? We favour mature projects with stable releases and long support windows.

  2. Hiring pool

    Could another team take it over? Widely used technology keeps you from being locked in, including to us.

  3. Performance

    Does it meet the load and latency the system needs, measured on realistic data rather than a benchmark page?

  4. Security updates

    Are vulnerabilities fixed quickly and published openly? We track advisories for everything we run.

  5. Fit for the problem

    The right tool for this system. Sometimes that means extending your existing PHP platform rather than rewriting it.

Reference architecture

A typical platform, end to end.

The shape most of our platforms share, adapted per project. A booking platform like Nazarene Tours follows the same path, with flight and hotel supplier APIs as its integrations.

Illustrative

Requests in

  • Browsers

    HTTPS

  • Mobile apps

    HTTPS · API

  • Edge

    CDN · WAF · DNS · SSL

  • Platform webhooks

    Meta · supplier platforms

Monitored

Application

Next.js or React front · Node.js or PHP API, behind Nginx on Linux

Behind the application

  • Redis

    cache · sessions · queues

  • MySQL or PostgreSQL

    primary data

  • Integrations

    REST · webhooks · official APIs

  • AI layer

    permissioned · logged

Operated by Comark

Linux · Nginx
  • Monitoring

    Uptime, resources and security events

  • Backups

    Off-site, restore-tested

  • Patches

    OS and security updates

  • Deploys

    Staging, then production

Integrations catalogue

Systems we connect to.

A selection of platforms we've integrated in production. If yours has an API, we can usually connect it. Ask us about it.

3Travel suppliersAmadeus · Travelport · Gimmonix
  • Amadeus

    Flight search and availability across airlines.

    Nazarene Tours
  • Travelport

    Flight content queried in parallel with other suppliers.

    Nazarene Tours
  • Gimmonix

    Hotel search and packages, with refundability terms.

    Nazarene Tours
1MessagingMeta Graph API · WhatsApp Business Platform
  • Meta Graph API · WhatsApp Business Platform

    Official WhatsApp, Instagram and Messenger messaging, templates and webhooks.

    Engage
1TelephonyTwilio
  • Twilio

    Browser calls, inbound routing and recordings linked to CRM records.

    Nazarene Tours
2AnalyticsGoogle Analytics 4 · Google Search Console
  • Google Analytics 4

    Events, conversions and e-commerce tracking.

    SEO and analytics
  • Google Search Console

    Indexing, search queries and technical SEO monitoring.

    SEO and analytics
1MapsGoogle Maps
  • Google Maps

    Locations and map-based interfaces.

    Websites
2Media and publishingBunny CDN · Pushwoosh
  • Bunny CDN

    Cache purge and media delivery for a newsroom that publishes all day.

    Kul al-Arab
  • Pushwoosh

    Push notifications to the iOS and Android apps.

    Kul al-Arab

Architecture review

A second opinion on the stack you inherited.

We'll review what you have, tell you what's worth keeping and plan how to modernise the rest, without a rewrite for its own sake.