Inteeka
Security advisory.PHP2Shell affects the software behind most websites. Free check: is yours exposed?Check now ›

How we build

Fast, safe and joined up.

The stack, the security and the integrations behind everything we ship, and the habits that let us release every day without asking customers to put up with breakages.

Integrations

Plays well with what you already use.

Most of the value is in the joins: email, payments, carriers, calendars, models and machines talking to each other, so people stop copying things between screens.

Email

Transactional email with delivery events, inbound email turned into tickets and drafts, and the sender’s own mailbox for replies a person approves. Domains are authenticated so mail lands in the inbox, not spam.

  • Postmark
  • Resend
  • Google Workspace
  • React Email

Payments and finance

Card and wallet payments, payment links on invoices, webhooks that answer fast and retry from an outbox, and the books kept in step.

  • Stripe
  • Apple Pay
  • Google Pay
  • Xero

Delivery and logistics

National, same-day and tracked-post carriers booked by API, address lookup at checkout, and labels printed at the bench.

  • Carrier APIs
  • Address lookup
  • Label printers
  • Barcode and QR scanning

Calls, messages and calendars

Video consultations with a phone fallback, text messages, booking pages and the host’s own calendar kept in sync.

  • Daily
  • Twilio
  • Cal.com
  • Google Calendar

AI models

Frontier models for reading, drafting and analysis, wired in through SDKs, with prompts and guardrails kept in code and reviewed like any other change.

  • Anthropic Claude
  • Google Gemini
  • Vercel AI SDK
  • OCR

Data and analytics

Analytics and search data pulled by API into our own reports, session replays reviewed for friction, and new features behind switches.

  • Google Analytics 4
  • Search Console
  • Session replay
  • Feature flags

Machines and devices

Production files dropped into the machines’ own hot folders, cutting tables fed layered files, and TV boards, kiosks and scan stations on the floor.

  • Print RIP hot folders
  • Flatbed cutters
  • Wall boards and kiosks
  • Scan stations

Our own building blocks

A feedback widget on every internal screen, a staff portal, and APIs between our platforms: the training client’s shop sends approved work to print with signed links.

  • Feedback widget
  • Staff portal
  • Signed links
  • Webhooks

How we connect things.

Verified at the door

Every incoming webhook is checked for its signature before anything acts on it.

Never lost, never doubled

Outgoing work goes through an outbox that retries, and each event is processed once even if it arrives twice.

Fast to answer

Webhooks are acknowledged at once and the slow work happens after, so providers never time out.

Tested against the real thing

Sandboxes and recorded responses in the test suites, then a live check after release.

Infrastructure stack

Six layers, one way of working.

Modern, managed and boring in the best way: proven tools, run close to the data, with every layer covered by the same tests, previews and release records.

  1. Experience

    Fast, accessible interfaces in React and Next.js, written in TypeScript, styled with Tailwind, with content managed in Payload CMS.

    • Next.js
    • React
    • TypeScript
    • Tailwind CSS
    • Payload CMS
  2. Compute and delivery

    Serverless functions and scheduled jobs on a global edge network, run close to the data, with a live preview of every change.

    • Vercel
    • Edge network
    • Cron jobs
    • Preview deployments
  3. Data

    PostgreSQL with row-level security and realtime updates, Redis for rate limits, and object storage for files.

    • PostgreSQL
    • Supabase
    • Redis
    • Object storage
  4. Intelligence

    Frontier models for drafting, reading and analysis, called through SDKs, with a person in the loop wherever the outcome matters.

    • Claude
    • Gemini
    • AI SDK
  5. Engineering

    Code review on every change, continuous integration on our own Apple silicon machines alongside hosted runners, and browser tests in Playwright.

    • GitHub
    • GitHub Actions
    • Playwright
    • Vitest
  6. Operations

    Alerts on the moving parts, nightly backups checked each morning, release records, and the office’s devices on a private network.

    • Monitoring and alerts
    • Backups
    • Release records
    • Private network

Security protocols

Secure by habit, not by audit week.

Security is part of every change rather than a phase at the end: the same checks run on the first line of a feature and on the thousandth release.

Certified

ISO 27001 for information security, alongside ISO 9001 and ISO 14001, independently audited.

Least privilege

Row-level security on every table, scoped and expiring keys, and staff roles that see only what their job needs.

Secrets never in code

Secret scanning on every change, and keys held by the hosting platform rather than in the repository.

Dependencies watched daily

A daily audit of every package, with updates proposed automatically when a fix is published.

Files scanned on arrival

Every upload is scanned for malware before a person or a machine opens it.

Sensitive data sealed

The most sensitive records are encrypted in the database, on top of encryption in transit and at rest.

Bots and abuse kept out

Bot protection, rate limits and human checks on the forms that attract abuse.

Signed links

Approval pages, files and hand-offs travel on signed links rather than open addresses.

Backups you can restore

Nightly database and storage backups, checked every morning.

Consent recorded

Analytics wait for cookie consent, and marketing consent is stored with when and how it was given.

Reviewed, not assumed

Full security reviews of our platforms, with every high and medium finding closed.

People in the loop

AI drafts and proposes; a person approves anything a customer will see, unless it is in a class we pre-authorised.

ISO 27001 certified (ISOQAR, UKAS accredited)ISO 27001ISO 9001 certified (ISOQAR, UKAS accredited)ISO 9001ISO 14001 certified (ISOQAR, UKAS accredited)ISO 14001

Ship speed

Shipped daily. Often hourly.

Speed is not recklessness. It comes from small changes, a preview of every one, and the confidence that the tests will catch what a person might miss.

4,800+

changes merged to production this year, on one platform

540+

in the last seven days alone

Minutes

from an approved change to customers seeing it

Small changes

One idea per change, so each is easy to review and easy to undo.

A preview of everything

Every change gets its own live preview before it reaches customers.

Rules become tests

When the owner sets a rule, it is written down and enforced by a test.

A record of every release

What changed, why, and how it was checked, kept for every deployment.

Switches, not launches

New features ship dark and go on sale when the business is ready.

Fast roll-back

If something misbehaves, the previous version is back in moments.

Testing

Tested before it is trusted.

Every change passes the same gates before it reaches a customer. Layer by layer, the suite checks that the code is sound, the business rules still hold, the customer journeys still work and the data is safe.

3,300+

automated test files

~3 min

for 65 end-to-end journeys

  1. 01

    Type checks and linting

    On every change, before anything else runs.

  2. 02

    Unit and integration tests

    3,300+ test files across the platform.

  3. 03

    Pinned outputs

    Prices, documents and production files frozen in tests, so a change elsewhere can never quietly move them.

  4. 04

    End-to-end journeys

    65 customer journeys walked in a real browser, in about three minutes a run.

  5. 05

    Security gates

    Secret scanning on every change and dependency audits every day.

  6. 06

    Backups, checked

    Nightly backups, verified every morning.

  7. 07

    Phone and accessibility checks

    Every page change is looked at at phone width before it ships.

Want this discipline on your product?

We can build it with you, embed with your team, or connect what you already run.