What we do · 02 · Technology & Intelligence

Your software and AI, built securely and kept running.

Websites, apps, software and AI that run your business.

Services
10
Scope
Plan, build, support
AI drafts
Engineer-checked

An illustrative diagram of your systems in four layers: Experience (Websites & Apps, Search & AI Visibility); AI & automation (AI Strategy & Agents, AI Product & Automation); Software & data (Custom Software & Data Platforms, AI Infrastructure & Cloud, Integration & Support); Trust & operations (Cybersecurity & AI Trust, Audits & Assessments, Tech Workforce). Requests move between the services. A status bar shows a 212-millisecond response time and 148 of 148 AI tests passing. It also shows 71 percent of the outage budget left and 0.18 grams of CO2e per request.

Why now

Software, data and AI now have to stay fast, secure and affordable every day.

4 shifts drive this: AI in products, monthly model changes, AI answers in search, and stricter security and privacy laws. Each card names its public source.

Screens marked Illustrative are examples, not client results.

A data-centre aisle lined with rack servers Where your software runsYour cloud account and region, monitored at every layer
  1. Then: A trial. Now: In the product.

    LLM01

    Top risk: AI tricked by hidden text

    AI inside the product

    AI features now talk to your customers, and they fail in ways normal testing misses.

    What we do about it

    We test AI on your own examples and add safety checks. A named person approves each release.

    04AI Product

    Source · OWASP Top 10 for LLM Applications, 2025

  2. Then: ~4k. Now: 1M+ word pieces.

    1M+

    How much text an AI reads at once

    Models change every month

    Limits, prices and rankings change faster than release plans, so every change needs testing.

    What we do about it

    One link, our AI gateway, reaches every model, so switching needs no rebuild.

    03AI Strategy

    Source · Provider model documentation, 2023–2025

  3. Then: 10 blue links. Now: 1 answer.

    10 → 1

    Ten blue links became one answer naming a few sources

    AI answers in search

    AI Overviews, ChatGPT and Perplexity answer directly and name a few sources. Being named takes technical work.

    What we do about it

    We make your pages easy to quote and report where you appear. Nobody can guarantee it.

    08Search

    Source · Google, OpenAI and Perplexity product pages

  4. Then: Annual audit. Now: Hours to report.

    6 h

    To report a cyber incident in India

    Security and privacy law

    India's data law (DPDP Act 2023), the EU AI Act and CERT-In's six-hour rule can apply to your software.

    What we do about it

    We build in consent checks, AI labels, security tests and activity logs, so proof is ready at launch.

    06Security

    Source · CERT-In Directions, 28 April 2022

How it works

Your systems in 4 layers we build and run.

Each service builds one or more layers. Pick a layer to see which, or follow one customer question through all 4.

Your systems in 4 layers. Experience: website and web app, mobile app, support chat, search and AI answers. AI and automation: support agent, document search, workflow automation, tests. Software and data: custom apps and CRM, customer data, tool connections, AI gateway, cloud and AI chips. Trust and operations, beside every layer: security and safety checks, live monitoring, audits and the on-call team. The steps below follow one question.

Who builds what

10 service pages, 4 layers

Our usual core tools

  • Kubernetes
  • Terraform
  • PostgreSQL
  • Apache Kafka
  • OpenTelemetry

AI models · one gateway, easy to swap

  • OpenAI
  • Anthropic
  • Google Gemini
  • Meta Llama
  • Mistral AI

L1 · built by 2 services

Experience

What customers see: websites, mobile apps, chat, search and AI answers.

L2 · built by 2 services

AI & automation

AI agents, answers from your documents and automated tasks inside the product.

L3 · built by 3 services

Software & data

Custom apps, a CRM, customer data, links between tools, the AI gateway and cloud.

One request, step by step Illustrative

  1. 01 A customer asks the support assistant on the website. 0 ms
  2. 02 The AI gateway, one link to several models, picks a small one first. 38 ms
  3. 03 The assistant looks up the customer's record in your customer data. 96 ms
  4. 04 Automatic safety checks read the answer before it is sent. 131 ms
  5. 05 The answer appears on screen and every step is logged. 212 ms
  6. 06 Each month we review a sample of logs like this one. sampled
  7. 07 If anything slips, the team on call fixes it. owned

Planning demo

5 common goals, each with a typical plan.

Pick a goal to see a typical plan: services, steps, team, checks and measures for the first 90 days.

Planning demo · Your company · draft plan Plan ready Typical ranges

Plan: Launch an AI support assistant · 6 phases · 12 weeks · 6 services

Architecture · services involved6 of 10

The services involved in the selected plan are highlighted on the map and numbered in build order.

Plan 1 of 5 · typical

Launch an AI support assistant

Answers customers from your own documents and records, and passes to a person when unsure.

Weeks
12
Phases
6
Services used
6
  1. 03 Choose the job and check risksAI Strategy Wk 1–2
  2. 02 Documents & CRM data readyPlatforms Wk 2–4
  3. 04 Assistant tested on examplesAI Product Wk 3–8
  4. 05 AI gateway & cost limitsAI Infrastructure Wk 6–9
  5. 06 Attack tests & OWASP LLM Top 10Security Wk 7–8
  6. 07 Human handoff & ongoing supportIntegration Wk 9–12 →

Team

  • AI lead
  • Product designer
  • 2 × AI engineers
  • Data engineer
  • Security engineer
  • Your support-operations lead

Checks · must pass

  • True to sources ≥ 0.90 on your examples
  • No critical flaws in attack tests
  • Replies in 2.5 s; first words in 0.8 s
  • Passes to a person when unsure

First 90 days · we measure

  1. 01Share solved by AI
  2. 02Cost per solved question
  3. 03Customer rating of AI chats

Standards this plan is built to

  • OWASP Top 10 for LLM Applications — Security risks in generative AI applications
  • NIST AI RMF 1.0 — AI Risk Management Framework
  • ISO/IEC 42001:2023 — Artificial intelligence management systems
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023

Plan 2 of 5 · typical

Replace an old CRM

A CRM is one place for every customer, enquiry and sale. We move yours over while sales carry on.

Weeks
18
Phases
6
Services used
6
  1. 09 Data & process auditAudits Wk 1–3
  2. 02 Data model & CRM buildPlatforms Wk 3–14
  3. 01 Sales & service screensWeb & Apps Wk 5–14
  4. 07 Links to ERP, email & phone systemsIntegration Wk 6–14
  5. 06 One log-in, access rules & activity logSecurity Wk 8–12
  6. 10 Switch-over & extra supportWorkforce Wk 14–18

Team

  • Solution architect
  • 3 × full-stack engineers
  • Data engineer
  • Integration engineer
  • Test engineer
  • Your sales-operations owner

Checks · must pass

  • Every moved record checked against the old
  • Two side-by-side runs, no serious bugs
  • Who-sees-what rules checked and approved
  • Undo plan rehearsed before switch-over

First 90 days · we measure

  1. 01Time from enquiry to quote
  2. 02Duplicate record rate
  3. 03Weekly active users

Standards this plan is built to

  • ISO/IEC 27001:2022 — Information security management systems
  • SOC 2 — Trust Services Criteria
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  • OWASP ASVS — Application Security Verification Standard

Plan 3 of 5 · typical

Make the product fast on real phones

Good Google speed scores from real visits, on the mid-range Android phones most customers carry.

Weeks
10
Phases
6
Services used
5
  1. 09 Speed audit on real visitsAudits Wk 1–2
  2. 01 Size limits for images, fonts & codeWeb & Apps Wk 2–6
  3. 05 Caching near your usersAI Infrastructure Wk 3–6
  4. 01 Fixes so pages show fasterWeb & Apps Wk 4–9
  5. 08 Search checks on every page typeSearch Wk 6–9
  6. 07 Auto size checks & live speed trackingIntegration Wk 8–10 →

Team

  • Performance lead
  • 2 × frontend engineers
  • Platform engineer
  • Search specialist

Checks · must pass

  • Main content in 2.5 s on most visits
  • Taps answered in 0.2 s
  • Layout stays put
  • Code size limit checked on every change

First 90 days · we measure

  1. 01Load time on low-cost Android
  2. 02Mobile visit-to-sale rate
  3. 03Unpaid search visits on mobile

Standards this plan is built to

  • Core Web Vitals — Loading, interactivity and visual stability
  • WCAG 2.2 AA — Web Content Accessibility Guidelines
  • SCI · ISO/IEC 21031:2024 — Software Carbon Intensity

Plan 4 of 5 · typical

Get named in AI answers

Pages that Google can rank and AI Overviews, ChatGPT and Perplexity can quote. Nobody can guarantee it.

Weeks
12
Phases
6
Services used
5
  1. 09 Check where you show up todayAudits Wk 1–2
  2. 08 Map of buyer questionsSearch Wk 2–4
  3. 01 Technical SEO & page labelsWeb & Apps Wk 3–7
  4. 08 Pages written to be quotedSearch Wk 4–12
  5. 02 Product & company data feedsPlatforms Wk 5–9
  6. 07 Test-question tracking & reportsIntegration Wk 8–12 →

Team

  • Search lead
  • Content strategist
  • Technical SEO engineer
  • Data engineer
  • Analyst

Checks · must pass

  • Correct page labels on every key page type
  • Google speed scores good
  • Facts consistent across site, feeds and profiles
  • Starting point recorded before changes

First 90 days · we measure

  1. 01How often AI names you on set questions
  2. 02Mentions per AI tool
  3. 03Sales and enquiries from search and AI

Standards this plan is built to

  • Core Web Vitals — Loading, interactivity and visual stability
  • WCAG 2.2 AA — Web Content Accessibility Guidelines
  • GDPR — General Data Protection Regulation (EU) 2016/679

Plan 5 of 5 · typical

Add AI engineers to your team

Vetted AI engineers join your team and release a first AI feature, tested from day one.

Weeks
12
Phases
6
Services used
5
  1. 10 Roles defined & team matchedWorkforce Wk 1–2
  2. 03 To-do list of AI jobs, rankedAI Strategy Wk 1–3
  3. 06 Access, data handling & AI policySecurity Wk 2–3
  4. 10 Settling into your teamWorkforce Wk 3–4
  5. 04 First AI feature goes liveAI Product Wk 4–10
  6. 09 Quarterly review of work & AI readinessAudits Wk 12 →

Team

  • Team lead
  • 2 × AI engineers
  • ML & data engineer
  • Test engineer for AI
  • Your product owner

Checks · must pass

  • Background checks & confidentiality signed
  • Only the access each person needs
  • AI tests run automatically before release
  • Speed and quality reported from the start

First 90 days · we measure

  1. 01Time from change to live
  2. 02Releases needing a fix
  3. 03AI features live per quarter

Standards this plan is built to

  • ISO/IEC 27001:2022 — Information security management systems
  • ISO/IEC 42001:2023 — Artificial intelligence management systems
  • DORA metrics — Software delivery performance

Phases and lengths are typical. We agree scope and price with you before work starts.

Tools we use

The technology we work with, by group.

174 technologies in 18 groups, from languages to team tools. We are not tied to one model or cloud, and pick what tests best.

Technologies we work with. A logo here does not mean we are a partner or reseller, or hold a certificate.

Group

174 technologies · 18 groups

In every group, we choose on evidence, write down why and keep each choice reversible.

Use the arrow keys to move between technologies; the selected technology is described in the panel beside the wall.

TypeScript Typed front ends and Node services JavaScript The browser and everything that runs in it Python AI, data pipelines and fast back ends Go High-throughput services and CLIs Rust Performance-critical components and WebAssembly Kotlin Android apps and JVM services Swift iOS and iPadOS apps PHP Content sites and mature web platforms Java Enterprise back ends on the JVM .NET Enterprise back ends on Windows and Linux Node.js API servers, workers and tooling
React Interactive product interfaces Next.js Server-rendered React sites and apps Vue.js Progressive interfaces on existing sites Angular Large internal applications with strict structure Svelte Lightweight embedded widgets and dashboards Astro Content-heavy sites with minimal JavaScript Tailwind CSS Token-driven styling at speed Three.js 3D views and product configurators in the browser WebAssembly Near-native compute in the browser
Flutter One codebase for iOS and Android React Native Mobile apps that share logic with React web Expo Faster React Native builds, updates and releases iOS Native Apple platform features Android Native Android platform features Jetpack Compose Modern native Android interfaces
NestJS Structured TypeScript APIs FastAPI Python APIs that serve models and data Django Admin-heavy platforms with a mature ORM Laravel PHP platforms with a rich ecosystem Spring Boot JVM services in enterprise environments GraphQL One typed API over many back ends OpenAPI Initiative API contracts that generate clients and tests Redis Caching, rate limits and queues RabbitMQ Reliable work queues between services Temporal Durable workflows that survive failures Supabase Postgres, auth and storage for fast starts Firebase Mobile back ends, push and analytics
PostgreSQL The default system of record MongoDB Document stores for flexible schemas Snowflake Cloud warehouse for analytics at scale Databricks Lakehouse for data engineering and ML Apache Spark Distributed batch and stream processing Apache Kafka The event backbone between systems Apache Airflow Scheduled data pipelines with lineage dbt Tested, versioned transformations in the warehouse ClickHouse Sub-second analytics on event data Elasticsearch Full-text search and log analytics Google BigQuery Serverless warehouse on Google Cloud DuckDB Fast local analytics inside pipelines Airbyte Connectors that move data into the warehouse Looker Governed metrics and dashboards Power BI Reporting inside Microsoft estates
PyTorch Training and fine-tuning models TensorFlow Production ML in Google-centred stacks Hugging Face Open models, datasets and tokenisers scikit-learn Classical ML: forecasting, scoring, clustering NVIDIA GPU compute for training and inference MLflow Experiment tracking and model registry vLLM High-throughput serving for open models Ray Distributed training and batch inference ONNX Portable models across runtimes Jupyter Exploration and reproducible analysis
OpenAI Top-tier models behind the gateway Anthropic Top-tier models for long documents and agent work Google Gemini Multimodal models and Google Cloud integration Mistral AI Efficient open-weight and hosted models Meta Llama Open-weight Llama models run in your cloud DeepSeek Open-weight reasoning models, self-hosted Ollama Local models for development and offline use Perplexity Search-grounded answers and citation tracking
LangChain Chains, tools and integrations for LLM apps LangGraph Stateful agents with checkpoints and approvals LlamaIndex Document ingestion and retrieval pipelines Pinecone Managed vector search at scale Weaviate Hybrid vector and keyword search Qdrant Self-hosted vector search with filtering Milvus Vector search for very large collections pgvector Vectors inside Postgres, no new database Replicate Hosted open models by API Modal Serverless GPUs for batch and bursty inference GitHub Copilot AI pair programming in the IDE Cursor AI-native code editing with review
AWS Primary cloud for most regulated workloads Microsoft Azure Cloud for Microsoft-centred estates Google Cloud Cloud for data- and AI-heavy platforms Cloudflare Edge, DNS, WAF and bot management Vercel Hosting for Next.js front ends Netlify Hosting for static and Jamstack sites DigitalOcean Simple cloud for smaller workloads Fastly Edge caching and compute Akamai Global delivery and edge security
Docker Reproducible builds and local environments Kubernetes Orchestration for services and model serving Helm Packaged Kubernetes deployments Terraform Infrastructure as code across clouds Pulumi Infrastructure as code in TypeScript or Python Ansible Configuration for hosts and appliances Argo GitOps delivery and workflow pipelines GitHub Actions Automatic tests, AI tests and scans GitHub Source, reviews and the audit trail GitLab Source and CI in self-hosted estates Jenkins CI in established enterprise pipelines Istio Service mesh for mTLS and traffic policy
OpenTelemetry Traces, metrics and logs on an open standard Prometheus Metrics and alerting for services Grafana Reliability dashboards for engineers and leaders Datadog Managed observability across cloud estates Sentry Error tracking in front ends and apps New Relic APM in established enterprise stacks Elastic Log analytics and security events PagerDuty On-call rotation and incident response
Playwright End-to-end tests in real browsers Cypress Component and end-to-end tests Selenium Cross-browser tests in legacy suites Jest Unit tests for JavaScript and TypeScript k6 Load tests before every launch Postman API contract tests and collections SonarQube Code quality and security gates in CI
Okta Enterprise SSO and identity Auth0 Customer identity and access OpenID Standard sign-in across systems JWT Signed tokens between services Vault Secrets management and dynamic credentials Snyk Dependency and container vulnerability scanning Trivy Image, IaC and SBOM scanning in CI Falco Runtime threat detection on Kubernetes OWASP ASVS, Top 10 and LLM Top 10 as the test bar Burp Suite Manual penetration testing 1Password Shared secrets for teams, never in chat
Zapier Quick automations between SaaS tools Make Visual automations with branching logic n8n Self-hosted workflow automation with AI steps MuleSoft Enterprise integration platform Kong API gateway, auth and rate limiting Twilio SMS, voice and verification WhatsApp Customer conversations on WhatsApp Business Slack Alerts, approvals and copilots where teams work Microsoft Teams Approvals and bots inside Microsoft 365
Salesforce CRM integrations and custom objects HubSpot CRM and marketing automation Zoho CRM and operations suites for the mid-market SAP ERP integration for orders, stock and finance Shopify Commerce storefronts and headless builds WooCommerce Commerce on WordPress Stripe Payments, billing and subscriptions Razorpay Payments and UPI for India PayPal Global checkout and payouts Intercom Customer messaging and support inbox Zendesk Support desk integration and AI handoff
Google Search, Ads and Maps platform APIs Google Search Console Index coverage and query data Google Analytics Traffic, conversion and attribution Google Tag Manager Consent-aware tag management PageSpeed Insights Field and lab Core Web Vitals Lighthouse Performance and accessibility audits in CI Semrush Keyword and competitor research Ahrefs Backlinks and content gaps Algolia Site and product search PostHog Product analytics, flags and session replay Mixpanel Product analytics and funnels Schema.org Structured data machines can cite
WordPress Content sites and editorial teams Contentful Headless content across many surfaces Sanity Structured content with live preview Strapi Self-hosted headless CMS Webflow Marketing sites teams edit themselves
Figma Design source of truth and tokens Storybook Component library and visual tests Jira Delivery tracking in enterprise teams Confluence Runbooks and decision records Linear Fast issue tracking for product squads Notion Docs and lightweight planning Miro Architecture and workshop whiteboards

Standards

Frameworks we build to.

We build to these frameworks, so the work produces the proof auditors ask for. The badges are our own drawings. None is an official seal.

A hand ticking items on a handwritten checklist in a notebook
Evidence for auditorsEach check is ticked off against what an auditor will ask to see.Photo: Jakub Żerdzicki / Unsplash

Choose a framework to see what it covers, how we use it and which services apply it. Details follow the list.

01Security & privacy14 frameworks

02Safe AI use5 frameworks

03Quality & accessibility3 frameworks

04Sustainability & operations4 frameworks

Without a badge, we also use ISO/IEC 25010 for software quality and the FinOps Framework for cloud costs. NIST AI 600-1 and the NIST AI RMF guide AI risk. Our OWASP Top 10 for LLM Applications entry follows the 2025 list.

"Built to" describes how we work. It does not mean Xterra Edze holds a certificate. ISO 9001 and ISO 14001 cover whole organisations; we follow their practices. Certificates Xterra Edze holds: to be confirmed before launch.

Framework1 / 26

Security & privacy · Standard

ISO/IEC 27001:2022

Information security management systems · ISO / IEC

What it covers

Rules for managing information security risks, with 93 controls on organisation, people, buildings and technology.

How it shows up in our work

As we work, we review access, approve changes, check suppliers and keep logs for your auditor.

Security & privacy · Attestation framework

SOC 2

Trust Services Criteria · AICPA

What it covers

Controls for security, staying online, correct processing, confidentiality and privacy. Type I checks the design on one date. Type II checks it works over time.

How it shows up in our work

We record change approvals, access and incidents automatically, ready for your auditor.

Security & privacy · Framework

NIST CSF 2.0

Cybersecurity Framework · NIST

What it covers

Managing security risk in 6 parts: Govern, Identify, Protect, Detect, Respond and Recover.

How it shows up in our work

We compare your security with your target, then rank and cost the steps.

Security & privacy · Framework

CIS Controls v8.1

Critical Security Controls and Benchmarks · Center for Internet Security

What it covers

Security steps in order of priority, plus secure settings for cloud, containers and operating systems.

How it shows up in our work

We set up cloud accounts and servers to CIS Benchmarks and watch for unapproved changes.

Security & privacy · Standard

OWASP ASVS

Application Security Verification Standard · OWASP

What it covers

Security checks for web apps and links between tools, in 3 risk levels.

How it shows up in our work

We pick the level your risk needs, add its checks to each task and test them automatically.

Security & privacy · Awareness standard

OWASP Top 10

Web application security risks · OWASP

What it covers

The top website security risks, such as weak access control, harmful input and bad settings.

How it shows up in our work

We plan for attacks early, scan each change and test by hand before release.

Security & privacy · Framework

SLSA

Supply-chain Levels for Software Artifacts · OpenSSF

What it covers

Levels of proof that software was built safely, with a checkable build record.

How it shows up in our work

We sign each release, with a build record and parts list (SBOM) in SPDX or CycloneDX.

Security & privacy · Standard

PCI DSS v4.0.1

Payment Card Industry Data Security Standard · PCI Security Standards Council

What it covers

12 rules to protect card data wherever it is stored, used or sent.

How it shows up in our work

We limit where card data goes, with stand-in numbers and separate networks, then protect the rest.

Security & privacy · Regulation

HIPAA Security Rule

Safeguards for electronic protected health information · US HHS

What it covers

Policy, physical and technical safeguards for patients' electronic health data (ePHI).

How it shows up in our work

We limit access, record every action and encrypt health data. Each supplier signs a HIPAA agreement.

Security & privacy · Regulation

GDPR

General Data Protection Regulation (EU) 2016/679 · European Union

What it covers

Europe's data law: a legal reason to use data, people's rights, privacy by design, breach reports and risk checks.

How it shows up in our work

We build consent, time limits on data and people's requests into the product, with risk checks where needed.

Security & privacy · Law

DPDP Act 2023

Digital Personal Data Protection Act, 2023 · Government of India

What it covers

India's data law and its Rules: notice and consent, people's rights, breach reports and extra duties for significant firms.

How it shows up in our work

From the first release, we build consent records, notices and a way to handle requests from users in India.

Security & privacy · Standard

ISO/IEC 27701

Privacy information management systems · ISO / IEC

What it covers

Rules for handling personal data you collect, or process for someone else.

How it shows up in our work

We record where personal data is kept, for how long and who handles it.

Security & privacy · Regulation

CERT-In Directions 2022

Cyber incident reporting directions · CERT-In, Government of India

What it covers

India's cyber-security rules: report listed incidents in 6 hours, keep logs in India for 180 days and sync clocks.

How it shows up in our work

We set up incident steps, log storage and synced clocks to meet the deadlines.

Security & privacy · Directive

NIS2

Network and Information Security Directive (EU) 2022/2555 · European Union

What it covers

Europe's cyber-security rules for key organisations: risk measures, supplier security and staged incident reports.

How it shows up in our work

For clients it covers, we fit its risk and reporting steps into what we build and run.

Safe AI use · Standard

ISO/IEC 42001:2023

Artificial intelligence management systems · ISO / IEC

What it covers

Rules for managing AI in a company: policy, impact checks and controls on data and models.

How it shows up in our work

Before an AI tool goes live, we list it, check its impact and set its controls.

Safe AI use · Framework

NIST AI RMF 1.0

AI Risk Management Framework · NIST

What it covers

Managing AI risk in 4 parts: Govern, Map, Measure and Manage. A second guide covers generative AI (NIST AI 600-1).

How it shows up in our work

We test each AI job's risks on your own examples. A named owner approves each release.

Safe AI use · Regulation

EU AI Act

Artificial Intelligence Act (EU) 2024/1689 · European Union

What it covers

Europe's AI law sets rules by risk: banned uses, duties for high-risk AI and general-purpose models, and AI labels.

How it shows up in our work

We rate each AI job by risk early, and build in AI labels, records and human checks.

Safe AI use · Awareness standard

OWASP Top 10 for LLM Applications

Security risks in generative AI applications · OWASP GenAI Security Project

What it covers

Risks in AI apps, such as hidden instructions that trick the AI, data leaks and AI with too much power.

How it shows up in our work

Before any AI goes live, we attack it with tests for hidden instructions, data leaks and tool misuse.

Safe AI use · Knowledge base

MITRE ATLAS

Adversarial Threat Landscape for AI Systems · MITRE

What it covers

Known ways attackers target AI, collected from past attacks and research.

How it shows up in our work

We list likely attacks on your AI from ATLAS, then try them in tests.

Quality & accessibility · Standard

WCAG 2.2 AA

Web Content Accessibility Guidelines · W3C

What it covers

Rules that make websites usable by people with disabilities. Version 2.2 adds visible focus, tap size and easier log-ins.

How it shows up in our work

We check each change automatically and test main tasks by keyboard and screen reader.

Quality & accessibility · Metric set

Core Web Vitals

Loading, interactivity and visual stability · Google

What it covers

For 3 in 4 visits, pages show in 2.5 s, respond in 0.2 s and do not jump around.

How it shows up in our work

We check speed limits on every change and track visitors' speed on each page type.

Quality & accessibility · Standard

ISO 9001:2015

Quality management systems · ISO

What it covers

Rules for managing quality: clear processes, attention to risk and steady improvement.

How it shows up in our work

We agree what done means, review each other's work and use release checklists.

Sustainability & operations · Specification

SCI · ISO/IEC 21031:2024

Software Carbon Intensity · Green Software Foundation

What it covers

The carbon software causes per user or other unit, counting energy use and the making of hardware.

How it shows up in our work

We measure carbon per request, user or AI answer as a starting point.

Sustainability & operations · Metric set

DORA metrics

Software delivery performance · DORA (DevOps Research and Assessment)

What it covers

How often you release, how fast changes go live, failure rate and recovery time.

How it shows up in our work

We measure them in your release tools from week one and report them as numbers.

Sustainability & operations · Standard

ISO 14001:2015

Environmental management systems · ISO

What it covers

Rules for managing environmental impact, legal duties and steady improvement.

How it shows up in our work

We track hosting, device and data impact beside cost, with targets to cut it.

Sustainability & operations · Standard

ISO 22301:2019

Business continuity management systems · ISO

What it covers

Rules for keeping your business running in a crisis: plan, test and improve.

How it shows up in our work

We set recovery time and data-loss limits for each service, then test them in drills.

Where it applies · 6 of 10 service pages

Shared checks

One activity log, built to 6 frameworks.

We build access rules and activity logs once, across your system. The same logs map to clauses in 6 frameworks, which saves cost.

  • ISO/IEC 27001:2022Annex A 8.15 · Logging
  • SOC 2CC7.2 · Monitoring of system components
  • PCI DSS v4.0.1Requirement 10 · Log and monitor all access
  • HIPAA Security Rule§164.312(b) · Audit controls
  • CERT-In 2022ICT logs kept 180 days, in India
  • DPDP Act 2023§8(5) · Reasonable security safeguards

A live activity log. Each line shows who acted, what they did, on what, how they signed in, the result and a trace ID. It includes an AI agent using a tool, a blocked export and a person approving a release.

How we use AI

AI helps build your software, under 4 rules.

AI agents draft the plan, tests and release. Each change passes code tests, AI tests and security scans. Below, one task runs through 8 stages.

Two engineers at their desks, one reading code in an editor on a large monitor
Reviewed by peopleAI drafts code; an engineer reads every line before it goes in.Photo: Compagnons / Unsplash

An interactive build console. One task, adding refund status to a support assistant, runs through eight stages. An agent drafts the plan and the tech lead approves it. An engineer writes the code with an AI helper and submits change 1482. A test agent adds 14 tests. The AI tests pass 148 of 148 examples, with a true-to-sources score of 0.94. Security scans find nothing critical. A named engineer reviews and approves the change. An agent releases it to 5, then 100 percent of users. The live system is then monitored against its targets. Other tabs show the code changes, the AI test report and the activity log.

delivery / your-platform / XE-1482 · Refund status in the support assistant Live after 3 h 32 min

Stage 01 of 8Agent + person

Plan

From the ticket, an agent drafts how we agree it is done and the edge cases. The tech lead edits and approves.

Output6 criteria · 3 edge cases · approved

Stage 02 of 8Agent + person

Code

An engineer writes the change with an AI helper in the code editor, then submits it with a summary.

OutputPR #1482 · +212 −38 · 7 files

Stage 03 of 8Agent

Tests

A test agent writes automatic tests for the change. The engineer keeps the ones that earn their place.

Output+14 tests · coverage 81.2% → 84.6%

Stage 04 of 8Agent

Checks

The AI feature is tested on your own examples: sources, refusals, speed and cost, against the live version.

Output148 / 148 pass · true to sources 0.94

Stage 05 of 8Agent

Security

Scans check the code, its add-ons and any stored passwords, with hidden-instruction attacks (OWASP LLM01) included.

Output0 critical · 0 high · 0 secrets

Stage 06 of 8Person

Review

A named engineer reads the change, the AI test report and the scans, then approves or asks for changes. Agents cannot approve.

Waiting for a named engineer. Agents cannot approve.

Approved by the tech lead · 17:12 · logged

Stage 07 of 8Agent

Release

Goes live to 5% of users, then 25% and 100% while errors and speed hold. If they slip, it undoes itself.

Outputrollout 5% → 25% → 100% · none undone

Stage 08 of 8Agent + person

Monitor

Speed, reliability and AI quality are watched once live. The on-call engineer handles anything that slips.

OutputOnline 99.96% · on target · AI steady

#1482Answer refund status from the order system, hand off on low confidence

services/support/answer.py+14−1Drafted with an AI helper · reviewed by the tech lead

@@ -41,9 +41,24 @@ def answer(question: str, customer: Customer) -> Answer:
    context = retrieve(question, customer_id=customer.id, k=8)
    return llm.complete(PROMPT.format(q=question, ctx=context))
    if intent(question) == "refund_status":
        order = tools.orders.lookup(customer.id, scope="read")
        context.append(order.as_citation())
    draft = gateway.complete(
        route="support.answer",        # small model first, escalates on low confidence
        prompt=PROMPTS["answer@v14"], question=question, context=context,
    )
    checked = guardrails.check(draft, policy="support@v6")   # PII, claims, injection
    if checked.confidence < 0.62:
        return handoff.to_human(question, draft, reason="low_confidence")
    return checked.answer

Review noteThe AI can only read data. It hands over to a person at the level set in testing. Approved.

golden-set@v14 · 148 cases · judge calibrated against expert labelsAll gates pass

MetricThis branchAgainst the gateGateLive
True to source 0.94 ≥ 0.90 0.93
Answer relevance 0.91 ≥ 0.85 0.90
Citation accuracy 0.97 ≥ 0.95 0.96
Correct refusals 1.00 = 1.00 1.00
Hidden instructions blocked 24 / 24 = 24 22 / 22
Response time 1.9 s < 2.5 s 2.1 s
Cost per answer $0.004 ≤ $0.006 $0.005

Why it mattersModels and instructions change. The same 148 tests run on every change, so a drop in quality is stopped before customers see it.

TimeActorActionModel · promptReviewerResult
14:02 spec.agent Drafted acceptance criteria route:large · spec@v7 Tech lead Approved
14:31 ide.pair Suggested 38 lines in 3 files route:code Tech lead 31 kept
16:40 test.agent Generated 14 tests route:code · tests@v3 Tech lead 12 kept
16:46 eval.runner Ran golden set v14 judge@v5 — Pass
17:12 Tech lead Approved merge of PR #1482 — — Merged
17:34 deploy.agent Canary 5% → 100% — On-call Live

RetentionKept with each change and release, exportable to your security system and sampled in the monthly audit.

  • Agents propose, people approve

    Agents draft, test and release. A named engineer approves every change before it goes live.

  • Every AI action is logged

    The model, instructions, inputs, output and reviewer are kept with each change and release.

  • No client data in public training

    Business AI accounts with training switched off, in your region where required.

  • Passwords never reach the AI

    Passwords stay in a secure vault. Agents get limited, short-lived access.

What we track on every project · DORA metrics Illustrative

Time to go live
Measured in hoursTask to live for the run above: 3 h 32 min
How often we release
Daily when neededSmall, reversible changes, released in stages
Changes that fail
Tracked per releaseEvery undo is reviewed in writing
Recovery time
Tracked per incidentGuides and on-call from day one

Model updates

New models, tested within days of release.

We test each new model on your examples and switch only if it scores better or costs less. Changes go live weekly, after 4 checks.

Model log · last 12 months

9 new models, each tested on your examples

Test score
0.81 → 0.93
Cost per 1k requests
$2.40 → $1.02
Adopted
6 of 9
Median time to decision
2 days

A chart of the last twelve months. Nine model releases are marked along the top. The test score on your examples rises in steps from 0.81 to 0.93 as six are adopted. Over the same time, the cost per thousand requests falls from 2.40 to 1.02 dollars. Each release can be chosen to see how it was tested and what changed.

0.80 0.85 0.90 0.95

Weekly releases · 12 weeks Illustrative

Every Thursday, whatever passed the checks goes live

12 weekly releases. 11 went live, with 9 to 23 changes each. Week 7 was held because a refund test score fell from 0.92 to 0.86. The fix went live in week 8.

  • Testsparts · links · journeys
  • AI testsyour examples · every AI feature
  • Scanscode · add-ons · passwords
  • Rollout5% → 100% while targets hold

W7 held. A refund test score fell from 0.92 to 0.86. Nothing went live; the fix went out with W8.

11 of 12 releases went live1 held by AI tests0 rollbacks

Idea to agent · typical Typical ranges

From a clear problem to live use in about 6 weeks

  1. Day 0 Problem framed One task, one owner and one measure, plus how the work is done today. Owner signs the measure
  2. Day 2 Test version on real data A working agent on anonymised copies of your data, logged step by step. The team who does the work reviews outputs
  3. Day 5 Starting score A test set from your real cases, scored for quality, cost and speed. Go or stop, decided on the numbers
  4. Week 3 Trial with users Named users; a person approves every action; safety checks and spend limits on. Security and legal sign the safety rules
  5. Week 6 Live, with safety checks Released through the AI gateway with monitoring, guides and an activity log. Sponsor signs the release

How a project runs

From first call to software your teams run.

Product, engineering, AI and security people work in shared 2-week cycles. 4 checks decide when work moves on. Pick a phase to see its decision, team and AI tasks.

A 5-phase project plan. Discover: weeks 1 to 2. Design: weeks 2 to 4. Build: weeks 4 to 16. Launch: weeks 16 to 18. Run: from week 18. 4 lanes: product and design; engineering; AI and data; security and quality. Checks: system design approved after Design, security sign-off after Build, go-live after Launch and a 90-day review in Run.

LanePhase · typical
Product & design
Engineering
AI & data
Security & quality

Phase 01 · Wk 1–2

Discover

Ends in a decisionWhat to build first, what it must achieve and whether the data can support it.

What you get

  • The problem and success measures
  • A map of your systems today
  • Data and AI readiness check
  • Risk list and privacy check

Who takes part

Your sponsorYour product ownerDomain expertsProject leadSolution architectAI lead

Where AI helps

  • Turns interview notes and tickets into themes, with sources
  • Maps your systems and data flows from documents and code
  • Drafts a first risk list for people to review

Phase 02 · Wk 2–4

Design

Ends in a decisionThe system design, the build order and the checks the build must pass.

Check · System design approved

What you get

  • System design and a record of decisions
  • Prototype tested with users
  • AI test examples, test plan
  • Security design and likely attacks
  • Cycle plan with goals

Who takes part

Solution architectTech leadProduct designerSecurity engineerYour IT and security leads

Where AI helps

  • Drafts design options and trade-offs for the architect to decide
  • Makes draft screens from your shared design kit
  • Suggests AI test examples from past tickets

Phase 03 · Wk 4–16

Build

Ends in a decisionEvery 2 weeks: what this cycle delivers, shown working in a demo.

Check · Security sign-off

What you get

  • Working software every cycle
  • Code tests, AI tests and scans on every change
  • Guides written as features land
  • A decision log kept current

Who takes part

Tech leadEngineersProduct designerTest and AI-test engineerYour product owner, weekly

Where AI helps

  • Helps engineers write code; people review every line
  • Writes tests and change summaries
  • Runs AI tests on every change and flags anything worse

Phase 04 · Wk 16–18

Launch

Ends in a decisionGo live, with an undo plan rehearsed and on-call staff ready.

Check · Go-live

What you get

  • Peak-traffic test report
  • Independent security test report
  • Switch-over plan and undo rehearsal
  • On-call rota, guides and training

Who takes part

Release managerReliability engineerSecurity engineerYour support leadYour sponsor

Where AI helps

  • Checks AI answers against your team's decisions in a pre-launch trial
  • Watches the step-by-step release and undoes it if errors rise
  • Drafts release notes and training material

Phase 05 · Wk 18 →

Run

Ends in a decisionEvery month: what to improve next, decided on service targets, test results and cost.

Check · 90-day review

What you get

  • Monthly report: service targets, AI test results, cost and carbon
  • Incident reviews without blame
  • Ranked list of improvements
  • The 90-day review

Who takes part

Service ownerOn-call teamYour product ownerYour finance partner, for cloud cost

Where AI helps

  • Sorts alerts and drafts incident timelines
  • Watches AI test scores after model or data changes
  • Flags unusual costs and suggests a fix for approval
Two colleagues working through a diagram on a whiteboard Design · week 3Design options on the wall before any are built
  • 2-week cycles

    A goal per cycle, agreed with your product owner.

  • A demo every cycle

    Working software you can click through on a test site.

  • A decision log

    Each design choice written down, so it outlives the people who made it.

  • Guides before go-live

    Written as features land and rehearsed before launch.

Sustainability

Lower-carbon software, measured per request.

AI adds energy to every request. We measure carbon per request with the Software Carbon Intensity (SCI) standard, ISO/IEC 21031. What cuts carbon also cuts cost.

Wind turbines on the horizon at dusk Measured and reportedCarbon reduced by design, then measured
  1. 01

    Reported per unit of use

    SCI per request or per active user, with what is counted written down.

  2. 02

    No offsets in the figure

    The SCI standard leaves out certificates and offsets, so the figure counts only cuts we make.

  3. 03

    Choosing the cloud region

    We weigh speed, grid carbon and data location rules under the DPDP Act. We record the choice.

sci-report / your-platform / support.answer Illustrative

Region · grid intensity and round trip from Delhi users

India West is the default because it carries the widest service coverage of the Indian regions, which usually decides it. India North is cleaner and closer to Delhi users, so it wins wherever its services cover the workload. The choice is made per project; both keep data in India.

Practices

Where the carbon went · gCO₂e per request

0.18gCO₂e per request

62% below baseline · 179 g per 1,000 requests

  • Right-sized models

    A small model answers first and hands over to a large one only when unsure.

    Energy per request down 30–60% where used

  • Fewer AI calls

    Repeat questions get a saved answer; background jobs run in batches.

    Model calls down 20–40%

  • Timed for cleaner power

    Heavy AI jobs and reports run when and where power is cleaner, using live grid data.

    Job emissions down 10–30%

  • Lighter pages

    Every build checks size limits for images, fonts and code, so each visit sends less data.

    Page weight down 30–50%

  • Idle servers switched off

    Servers scale to zero overnight, sizes match the load and unused resources are deleted monthly.

    Idle spend and hardware carbon down

Typical effects are published ranges. Grid figures are illustrative yearly averages; live ones come from your cloud and grid data.

Industries

Sector rules built into the software.

Each sector has its own laws, rules on where data lives, speed needs and human review. We settle them before coding starts. Pick yours.

Sector01 / 08

Trading screens and a tablet showing market charts on a desk

01 · PCI DSS · RBI · SEBI

Financial services

Payments must be fast, and every decision needs a record.

Regulation
PCI DSS v4.0.1 for card data, RBI rules on IT outsourcing and SEBI's cybersecurity and cyber-resilience framework for market firms.
Where data lives
Payment data stays in India under RBI's 2018 direction; customer data follows the DPDP Act.
Speed & scale
Payment and trading systems answer 99% of requests in a few hundred milliseconds, even at salary-day and market-open peaks.
AI oversight
Every AI-assisted decision is logged with its inputs, model and reviewer. Credit decisions come with reasons.

Standards that apply

  • PCI DSS v4.0.1 — Payment Card Industry Data Security Standard
  • ISO/IEC 27001:2022 — Information security management systems
  • SOC 2 — Trust Services Criteria
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023

Typical first projectA security and AI-readiness audit, then a fraud-check assistant with human approval.

A doctor reviewing scans on a tablet with a patient

02 · HIPAA · DPDP · clinical safety

Healthcare & life sciences

Patient safety comes first, and health data needs the strictest care.

Regulation
DPDP Act consent and purpose limits in India. ABDM health-data standards where they apply. The HIPAA Security Rule for US patient data.
Where data lives
Health records stay in region; models are trained only on anonymised data.
Speed & scale
Tools for doctors answer within a consultation and work on weak signal at remote sites.
AI oversight
A clinician checks every AI suggestion about care and makes every clinical decision.

Standards that apply

  • HIPAA Security Rule — Safeguards for electronic protected health information
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  • ISO/IEC 27001:2022 — Information security management systems
  • ISO/IEC 42001:2023 — Artificial intelligence management systems

Typical first projectAI drafts visit summaries; the clinician signs off every note.

A shopper and a store assistant looking at products on a tablet

03 · Page speed · sale days

Retail & commerce

Sale-day traffic, mid-range phones and AI search answers shape revenue.

Regulation
PCI DSS through the payment provider, DPDP consent for marketing and consumer-protection rules on prices and claims.
Where data lives
Customer profiles in region; card data stays with the payment provider.
Speed & scale
Fast pages for 3 in 4 visits on mid-range Android phones. Sale days bring 10 to 20 times normal traffic.
AI oversight
Assistants answer from the live catalogue, so prices and stock match what is on sale.

Standards that apply

  • Core Web Vitals — Loading, interactivity and visual stability
  • PCI DSS v4.0.1 — Payment Card Industry Data Security Standard
  • WCAG 2.2 AA — Web Content Accessibility Guidelines
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023

Typical first projectFaster product and checkout pages, measured on real visits and sales.

A robotic arm on an automated production line

04 · Plant systems · on-site

Manufacturing

Plants run on control systems that cannot stop for an upgrade.

Regulation
IEC 62443 for industrial control-system security, ISO/IEC 27001 for IT and export controls on some designs.
Where data lives
Plant data stays on site; only summaries and models go to the cloud.
Speed & scale
Camera checks at line speed, run on site so they keep working if the network drops.
AI oversight
An engineer checks quality decisions until the AI is accurate on your own line.

Standards that apply

  • ISO/IEC 27001:2022 — Information security management systems
  • NIST CSF 2.0 — Cybersecurity Framework
  • ISO 22301:2019 — Business continuity management systems
  • ISO 9001:2015 — Quality management systems

Typical first projectJoin plant and stock systems, then a camera-check trial on one line.

Students gathered around a laptop in a lecture hall

05 · Children's data · accessibility

Education

Results days bring the peaks, and children's data needs the most care.

Regulation
The DPDP Act requires verifiable parental consent for under-18s and bars tracking or targeted ads at them. WCAG 2.2 AA covers accessibility.
Where data lives
Student records stay in region, kept only as long as needed.
Speed & scale
Results days bring 50 times normal traffic; pages work on slow connections.
AI oversight
AI tutors with safety checks and age-appropriate content, and teachers see everything.

Standards that apply

  • WCAG 2.2 AA — Web Content Accessibility Guidelines
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  • GDPR — General Data Protection Regulation (EU) 2016/679
  • OWASP Top 10 for LLM Applications — Security risks in generative AI applications

Typical first projectAn accessible student portal, load-tested for results day.

Shipping containers stacked in a port, seen from above

06 · Tracking · system links · offline

Logistics

Every shipment is an event, and every event has to reach the right system.

Regulation
Links to e-way bill and GST e-invoicing, and data-sharing agreements with carriers and partners.
Where data lives
Operating data in region; each partner sees only what its contract allows.
Speed & scale
Tracking updates arrive in seconds, and driver apps keep working offline.
AI oversight
Route and arrival-time models are watched for falling accuracy; problems go to a dispatcher.

Standards that apply

  • ISO/IEC 27001:2022 — Information security management systems
  • SOC 2 — Trust Services Criteria
  • ISO 22301:2019 — Business continuity management systems

Typical first projectOne live feed across carriers, warehouse and orders, with WhatsApp updates to customers.

Government buildings in New Delhi under a cloudy sky

07 · Data in India · audit · languages

Public sector

Data kept in India, accessibility and full records are needed from day one.

Regulation
CERT-In six-hour incident reporting and 180-day log retention, the DPDP Act and the GIGW guidelines for government websites.
Where data lives
Data held in India, on government-approved cloud where the department requires it.
Speed & scale
Citizen services in many Indian languages, with spikes as scheme deadlines approach.
AI oversight
A person reviews any decision about a citizen, and the explanation can be published.

Standards that apply

  • CERT-In Directions 2022 — Cyber incident reporting directions
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  • WCAG 2.2 AA — Web Content Accessibility Guidelines
  • ISO/IEC 27001:2022 — Information security management systems

Typical first projectA security and accessibility audit, then a multilingual citizen-service assistant.

Two engineers working side by side at monitors of code

08 · SOC 2 · data kept apart · AI

Software

Big buyers want security proof before they sign.

Regulation
Large buyers expect SOC 2 reports and ISO/IEC 27001. GDPR and the EU AI Act apply to EU customers.
Where data lives
Each client's data walled off; EU or India hosting on request.
Speed & scale
Speed targets per plan, and one busy client cannot slow the rest.
AI oversight
AI features keep each client's data separate and are tested on every release.

Standards that apply

  • SOC 2 — Trust Services Criteria
  • ISO/IEC 27001:2022 — Information security management systems
  • GDPR — General Data Protection Regulation (EU) 2016/679
  • EU AI Act — Artificial Intelligence Act (EU) 2024/1689

Typical first projectSecurity-review readiness, then an AI feature that keeps client data apart.

Our reports

A monthly report in numbers everyone reads the same way.

We report speed, reliability, AI quality, security, cost and carbon each month. Each number has a written definition and a target agreed before launch.

Service report · Xterra Edze

Your systems

Six measures · targets agreed before launch · a definition by every number Illustrative

01Speed On target

Load time · mobile, real visits

2.1s ▼ 1.7 s · 12 months

p95 response time212 ms

Definition · Speed

How long the main content takes to appear, for 75% of real page loads on mobile (LCP). Google's Core Web Vitals rate 2.5 s or less as good. p95 response time: 95% of requests finish faster than this.

02Reliability On target

Uptime vs target · last 30 days

99.97% ▲ 0.25 pts · 12 months

Outage budget left71% · 12.5 of 43.2 min used

Definition · Reliability

The share of requests served well over 30 days. A 99.9% target allows 43.2 minutes of failure a month: the outage budget. When it runs out, releases pause and reliability work comes first.

03AI quality On target

True to sources · test set

0.94 ▲ 0.10 · 12 months

AI tests passed148 / 148 cases

Definition · AI quality

The share of claims in an answer that its sources support. We call it true to sources. A judge model, checked against expert ratings, scores it. The same set of your real examples runs on every change to a model, instruction or data source. The hero readout, the build console and the planning demo all report this one figure.

04Security On target

Open critical security flaws

0 ▼ 6 · 12 months

Fix time · high severity3.2 days

Definition · Security

Confirmed critical flaws from scans, attack tests and reports, counted until the fix is checked live. Fix time is the average time from a flaw being confirmed to its fix going live.

05Cost On target

Cost per 1,000 requests

$1.02 ▼ $1.38 · 12 months

Spend vs monthly budget94%

Definition · Cost

Servers, AI usage, storage and data transfer, divided by requests served, per 1,000. Reviewed with finance every month using the FinOps Framework, because cost per request says more than the total bill.

06Carbon On target

SCI per request

0.18gCO₂e ▼ 0.29 g · 12 months

Jobs run at cleaner hours86%

Definition · Carbon

Software Carbon Intensity from the Green Software Foundation (ISO/IEC 21031:2024): energy, grid carbon and hardware, per request. Offsets are left out, so it falls only when the software uses less.

  1. Weekly

    Operations review

    Outage budget used, incidents, AI test scores and any call-outs, in 15 minutes with the on-call engineer.

  2. Monthly

    Service report

    All 6 measures against target, including cost and carbon, and next month's changes.

  3. Quarterly

    Business review

    The measures agreed before launch, the plan ahead and our delivery numbers (DORA).

Core Web Vitals (speed)
Loads in 2.5 s, reacts in 200 ms and barely shifts, for 75% of visits
Outage budget
99.9% over 30 days = 43.2 min of allowed failure
Early warning
1 h at 14.4× the safe rate uses 2% of the budget: alert on-call
p95 / p99
The time 95% or 99% of requests beat; averages hide the slowest ones

Where we work

Offices in India and Canada, overlapping your hours.

Together, our office hours overlap most of the working day in Europe, the Gulf, South-East Asia and North America.

Time zones
2India Standard Time (UTC+5:30) and Atlantic Time in Saint John (UTC−4, UTC−3 in summer)
Office hours
10:00–19:009 hours in India, Monday to Friday
Extended shift
+ 3.5 hTo 22:30 IST, by agreement
On call
24 / 7Rota and who to call, by agreement

Office 01 · India

New Delhi

00:09 IST · UTC+5:30

6 Worldmark, AerocityNew Delhi 110037, India

Work led here

  • Client and project leadership
  • System design and AI engineering
  • Security, audit and assessment work

Office 02 · India

Ludhiana

00:09 IST · UTC+5:30

SCO-2, LGFSCO-1, 3rd Floor Noble Enclave, Opp. Hotel Park PlazaFerozepur Road, Ludhiana, Punjab 141001, India

Work led here

  • Cloud, product and web engineering
  • Data, testing and AI checks
  • Managed service, support and the on-call rota

Office 03 · Canada

Saint John

14:39 AST · UTC−4

120 University AvenueSaint John, NB E2K 1Z3, Canada

Overlap

Your working day against ours, hour by hour

Offices · IndiaIST · UTC+5:30

9 hoffice hours

Office · CanadaSaint John · ADT · UTC−3Saint John · AST · UTC−4

Saint John office, Northern summer: open 09:00–17:00 ADT, which is 17:30–01:30 India time.Saint John office, Northern winter: open 09:00–17:00 AST, which is 18:30–02:30 India time.

United KingdomLondon · BST · UTC+1London · GMT · UTC+0

United Kingdom, Northern summer: a 09:00–17:30 local working day shares 8.5 h with our office hours. United Kingdom, Northern winter: a 09:00–17:30 local working day shares 8.5 h with our office hours.

EuropeFrankfurt · CEST · UTC+2Frankfurt · CET · UTC+1

Europe, Northern summer: a 09:00–17:30 local working day shares 8.5 h with our office hours. Europe, Northern winter: a 09:00–17:30 local working day shares 8.5 h with our office hours.

GulfDubai · GST · UTC+4Dubai · GST · UTC+4

Gulf, Northern summer: a 09:00–18:00 local working day shares 9 h with our office hours. Gulf, Northern winter: a 09:00–18:00 local working day shares 9 h with our office hours.

SingaporeSingapore · SGT · UTC+8Singapore · SGT · UTC+8

Singapore, Northern summer: a 09:00–18:00 local working day shares 5.5 h with our office hours. Singapore, Northern winter: a 09:00–18:00 local working day shares 5.5 h with our office hours.

US EastNew York · EDT · UTC−4New York · EST · UTC−5

US East, Northern summer: a 09:00–17:30 local working day shares 7 h with our office hours. US East, Northern winter: a 09:00–17:30 local working day shares 7 h with our office hours.

Working days shown as 09:00–17:30 local (09:00–18:00 in the Gulf and Singapore). Shared hours count office days in India and Saint John. Handovers are written down: open incidents, releases in progress and pending approvals.

Offers & plans

Technology services, bought alone or as one project.

Pick an offer to start with and your enquiry reaches the right team. Each comes as a short Sprint, a fixed-price Project or an ongoing team.

Categories
05
Offers
21
Plans
06
Not sure what you need? Tell us the problem

How to buy

  1. 01Pick offers. Ask about one, or add several to one enquiry.
  2. 02Choose a plan. A small job, a fixed project or ongoing help.
  3. 03Send your enquiry. We reply within one working day.

Browse by category

Timelines are typical. We write the scope before we quote.

01Build

4 offers
Typical timeline: 6–12 weeks

Website

A company, marketing or online-shop website that loads fast, works for everyone and is easy to update.

What’s included

  • Page templates and an easy editor
  • SEO basics and Schema.org markup
  • Speed and accessibility checks before launch
  • Analytics and consent set-up
  • Corporate
  • E-commerce
  • One editor

Best forCompanies launching a brand or replacing a site that holds them back.

Explore Websites & Apps
Typical timeline: 10–18 weeks

Web or mobile app

A web, iPhone or Android app, built per platform or once for both, as your product needs.

What’s included

  • Research and a clickable draft
  • Log-ins, roles and core features
  • Native, Flutter or React Native
  • Store submission, crash reporting and analytics
  • Web app
  • iOS · Android
  • Cross-platform
  • React Native

Best forFounders and product teams putting a new product in front of customers.

Explore Websites & Apps
Typical timeline: 12–24 weeks

Custom CRM or operations system

A CRM, operations system or approval tool built around how your business already runs.

What’s included

  • Process map and build-or-buy choices
  • Data design and access by role
  • Links to the systems you keep
  • Data moved over and checked
  • CRM
  • ERP
  • Internal tools
  • Salesforce

Best forBusinesses that have outgrown spreadsheets or off-the-shelf software.

Explore Custom Software & Data Platforms
Typical timeline: 8–16 weeks

Data & dashboards

Your business data in one place, with dashboards, so every team works from the same numbers.

What’s included

  • One store for all your data
  • Automatic feeds from your tools
  • Tested data, one definition per metric
  • Power BI or Looker dashboards
  • Data store
  • Feeds
  • Reports
  • dbt
  • Power BI

Best forLeadership teams reporting from spreadsheets that disagree.

Explore Custom Software & Data Platforms

02AI & automation

5 offers
Typical timeline: 4–6 weeks

AI strategy

A plan showing where AI can save time, cost or risk, what to build first and how to measure it.

What’s included

  • Interviews and process walk-throughs
  • Ideas scored on value, effort and risk
  • Step-by-step plan with business cases
  • Trial plan for the first project
  • Readiness
  • Where AI fits
  • Clear plan

Best forLeaders who want an AI plan built on their own processes.

Explore AI Strategy & Agents
Typical timeline: 8–12 weeks

Custom AI agent or helper

An AI agent that answers, drafts, checks and updates records in your systems. A named person approves anything important.

What’s included

  • Clear tasks and limited access
  • Links to your tools
  • Quality and attack tests before launch
  • Action log and human sign-off
  • Agents
  • AI helpers
  • Human approval
  • OpenAI

Best forTeams with repetitive, rules-heavy work spread across several systems.

Explore AI Strategy & Agents
Typical timeline: 6–10 weeks

Knowledge assistant

Ask your documents and data questions and get answers with sources shown, so people can check them.

What’s included

  • Your documents loaded and searchable
  • Sources shown, access rules kept
  • Tests that answers stick to sources
  • On the web, Slack or Teams
  • Document Q&A
  • Sources shown
  • Access rules
  • LlamaIndex
  • pgvector
  • OpenAI

Best forSupport, sales, HR and legal teams searching long documents every day.

Explore AI Product & Automation
Typical timeline: 2–8 weeks

Workflow automation

Data entry, paperwork and hand-offs between tools done automatically, with odd cases sent to the right person.

What’s included

  • Process map and what to automate
  • AI that reads, sorts and drafts
  • Error handling, alerts and activity log
  • Guides and team handover
  • n8n
  • Make
  • Temporal

Best forOperations teams losing hours to copy-and-paste work.

Explore AI Product & Automation
Typical timeline: 4–10 weeks

AI model hosting

Run AI models fast and at low cost, on cloud services or your own GPU servers. We track speed and cost per request.

What’s included

  • Hosted with vLLM or cloud services
  • Saved answers, batching and model choice
  • Load tests against speed targets
  • Cost-per-request dashboard
  • Model hosting
  • Response time
  • Cost per request

Best forProducts with growing AI use, data-location rules or rising AI bills.

Explore AI Infrastructure & Cloud

03Run & protect

5 offers
Typical timeline: 8–20 weeks

Cloud migration & foundations

Move to AWS, Azure or Google Cloud, or tidy what you already run there, on a secure, repeatable set-up.

What’s included

  • A move plan for each application
  • Secure access, network and rules
  • Set-up written as code
  • Switch-over with a way back
  • AWS
  • Azure
  • Google Cloud
  • AWS
  • Microsoft Azure

Best forOrganisations leaving a data centre or tidying their cloud.

Explore AI Infrastructure & Cloud
Typical timeline: 1–3 weeks

Security test (VAPT)

Specialists attack your website, app, API or cloud within agreed limits, then show you what to fix.

What’s included

  • Agreed scope and rules
  • Manual testing against OWASP guidance
  • Flaws ranked by risk, with proof
  • Fix advice and a retest
  • Web · mobile
  • API · cloud
  • OWASP

Best forBefore launch, after big changes or when customers ask for a report.

Explore Cybersecurity & AI Trust
Typical timeline: 8–24 weeks

Compliance readiness

Get ready for ISO/IEC 27001:2022, SOC 2 or India's DPDP Act 2023. We find and help close the gaps, and prepare evidence for your auditor.

What’s included

  • Gap check against the standard
  • Risk review and policies
  • Help putting controls in place
  • Evidence collection and audit support
  • ISO/IEC 27001:2022
  • SOC 2
  • DPDP Act 2023

Best forCompanies whose customers or regulators ask for proof of security.

Explore Cybersecurity & AI Trust
Typical timeline: 4–10 weeks

System integration

Link your sales, accounts, payment and other tools, so data is typed once and moves between them correctly.

What’s included

  • Map of links and data rules
  • Links that retry if they fail
  • Link tests and monitoring
  • Guides for your team
  • APIs
  • Connectors
  • Live sync
  • Salesforce
  • MuleSoft

Best forTeams typing the same data into several systems.

Explore Integration & Support
Typical timeline: Onboarding 2–4 weeks, then monthly

Managed support with SLAs

Engineers monitor your systems, respond to incidents within agreed times, keep everything patched and report monthly.

What’s included

  • Response and fix times by severity
  • Monitoring and alerting
  • Security patches and upgrades
  • Monthly service review
  • SLA
  • Monitoring
  • Monthly report

Best forBusinesses whose systems matter too much to run without cover.

Explore Integration & Support

04Grow & assess

4 offers
Typical timeline: 90-day cycles, ongoing

Ongoing SEO

Technical fixes, useful content and clear structure that help your site rank in Google and Bing.

What’s included

  • Technical SEO audit and fixes
  • Topic and content plan
  • Labels search engines read
  • Monthly reports from where you start
  • Technical SEO
  • Content
  • Reporting
  • Schema.org

Best forBusinesses where search is a main source of customers.

Explore Search & AI Visibility
Typical timeline: 8–12 weeks, then ongoing

Named in AI answers

Make pages easy for ChatGPT, Gemini and Google's AI Overviews to quote. We report where you appear. Nobody can guarantee it.

What’s included

  • Your starting point in AI answers
  • Clear answers and facts about you
  • Outreach to trusted sources
  • Monthly tracking of AI mentions
  • ChatGPT
  • Gemini
  • AI Overviews
  • OpenAI
  • Schema.org

Best forBrands whose customers now research by asking an AI assistant.

Explore Search & AI Visibility
Typical timeline: 2–4 weeks

Technical & code audit

An independent review of your code, system design and delivery process, with ranked fixes and what each problem costs you.

What’s included

  • Code and system design review
  • Security and add-on checks
  • Release speed and stability check
  • Ranked fixes and a 30-60-90-day plan
  • Code
  • System design
  • Tech debt

Best forBefore a funding round, rebuild, acquisition or supplier change.

Explore Audits & Assessments
Typical timeline: 2–4 weeks

AI readiness assessment

A scored review of how ready your data, systems, skills and rules are for AI, and what to fix first.

What’s included

  • Scores for data, systems, skills and rules
  • Which ideas are ready
  • Risk and compliance check
  • What to fix first
  • Readiness score
  • Fix-first list

Best forOrganisations planning an AI project or a first AI build.

Explore Audits & Assessments

05Talent

3 offers
Typical timeline: Start in 2–4 weeks

Dedicated team

Engineers, testers and designers under one lead. They work in your tools and schedule, and answer for an agreed result.

What’s included

  • Team shaped to the goal
  • A named lead and agreed goals
  • Work in your tools and meetings
  • Monthly progress review
  • Squad
  • Agreed outcome
  • Your schedule

Best forCompanies with a clear product goal but no spare team.

Explore Tech Workforce
Typical timeline: Start in 2–4 weeks

Engineers by role

Checked engineers join your team for as long as you need, for web, mobile, cloud, data or AI work.

What’s included

  • Engineers tested in your tools
  • You interview and choose
  • First code change accepted in week 1
  • Monthly quality and fit review
  • Extra engineers
  • Checked
  • Flexible

Best forTeams with more plans than people.

Explore Tech Workforce
Typical timeline: Ongoing, set days each month

Part-time CTO or tech lead

A senior tech leader for part of the week. They set direction, guide system design, lead hiring and brief your board.

What’s included

  • Technology strategy and a plan
  • System design, supplier choices
  • Hiring plan and interviews
  • Board and investor updates
  • Leadership
  • Part-time

Best forStart-ups and growing companies not yet ready for a full-time CTO.

Explore Tech Workforce

Your enquiry

Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

How we work with you

Ways to start, from a question to a quote.

Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.

Or book a 30-minute call

What are you sending?

  1. 01

    About 2 minutes3 short answers

    For a first chat, a press request or anything not ready to plan yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, who it is for, budget and timing, so our first reply can outline the work.

    You get Options and prices after one call

  3. 03

    About 15 minutesYour documents attached

    Your documents, deadlines and the purchasing and security rules to meet.

    You get Confirmation and a named lead

How it is priced

Each plan shows how it is priced. Work starts once we agree a written scope and price.

  • Typical length
    1–3 weeks
    Pricing
    Fixed fee
  • Typical length
    4–12 weeks
    Pricing
    Fixed price
  • Typical length
    3–9 months
    Pricing
    Fixed price per stage
  • Typical length
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
  • Typical length
    6–18 months
    Pricing
    Priced per written scope
  • Typical length
    Ongoing · 3-month minimum
    Pricing
    Paid by time used
Compare what each plan includes
What each plan includes and who it suits
PlanWhat you getBest for
SprintA short, fixed job that answers one clear question.
  • Scope and result agreed before we start
  • A senior lead and the right specialists
  • A weekly review with you
  • A clear answer or a test version
An audit, a brand check or a test version of an app
ProjectOne clear job for one fixed price.
  • A written scope: what you get and how we agree it is done
  • A named project lead and a fixed team
  • A shared plan with checkpoint dates
  • Source files, yours once paid for
A brand identity, a website, a simple app or a set of tools
MilestoneA bigger build in stages you approve and pay for one at a time.
  • Stages, each with its own scope and approval
  • A go or stop review at each stage
  • Re-plan between stages as you learn
  • Pay for each stage you approve
Work too big for one contract, such as a large app
RetainerA monthly team that runs and improves what we built.
  • Team time set aside for you every month
  • Agreed response times for requests and fixes
  • A monthly review and a to-do list
  • Planned improvements, not only fixes
Monthly social media and ads, or care for live sites and apps
EnterpriseA large, long project with its own team and agreed response times.
  • A project director and a decision group
  • A team for each part of the work
  • Response times, reports and a list of risks
  • Security, legal and purchasing checks in the plan
Large companies making changes across markets, brands or business units
SquadOur specialists join your team and work in your tools.
  • Named specialists matched to your plan
  • Works in your own tools and meetings
  • Grow or shrink the team each month
  • We teach your team from week one
Teams with a clear plan that need senior people fast

How we work with you

6 terms we build into the work.

The answers your legal, IT, security and buying teams ask for, each with the setting that enforces it.

Two engineers reviewing code together on a laptop Reviewed togetherDecisions written down as they are made
terms.md · Your company × Xterra Edze 6 clauses
  1. §1Usually asked by Legal · Procurement

    You own the code and the AI settings

    The code, cloud set-up, AI instructions, AI test examples and model settings sit in your code accounts from day one. All of it is yours once it is paid for.

    Enforced asrepository

    repo.owner    = "your-org"
    ip.assignment = "on payment"
    includes      = [code, iac, prompts, evals, model_config]
    
  2. §2Usually asked by CTO · Procurement

    Any AI model, easy to switch

    Every model sits behind our AI gateway and your test examples. Switching provider, or running a model yourself, is a settings change we can show you, not a rebuild.

    Enforced asgateway config

    route "support.answer" { model = var.model }
    switch.requires = "golden set ≥ gate"
    exit            = open formats, your keys
    
  3. §3Usually asked by Security · IT

    Secure from the first line of code

    Only the right people get access, with your one log-in where you have it. Passwords sit in a vault, every build is scanned and your security questions are answered before work starts.

    Enforced asCI policy

    ci.required = [sast, deps, secrets, iac, image]
    access      = sso + mfa, least privilege
    secrets     = vault only · never in prompts
    
  4. §4Usually asked by Security · Risk

    People approve, agents assist

    Agents draft, test and suggest. A named person approves every code change, every live change and anything that reaches your customers. Every AI action is logged.

    Enforced asbranch protection

    main.required_reviews = 1   # a named person
    agents.can_merge      = false
    ai_actions.log        = [model, prompt, reviewer]
    
  5. §5Usually asked by CTO · Finance

    Measured, not claimed

    Targets for speed, reliability, AI quality, security, cost and carbon are agreed before launch. We report them every month, good months and bad.

    Enforced asservice report

    report.monthly = [cwv_p75, slo_30d, evals, vulns,
                      cost_per_1k, sci_per_request]
    targets        = "agreed before launch"
    
  6. §6Usually asked by IT · Operations

    Guides and handover are part of the work

    Design decisions, step-by-step guides, dashboards and training notes are written as the work lands. You sign them off like any other part, so your team can run it without us.

    Enforced asdefinition of done

    done    += [adr, runbook, dashboard, alert, owner]
    handover = "rehearsed, not emailed"
    

Our work is built to ISO/IEC 27001, SOC 2 and ISO/IEC 42001. We do not claim certificates; only independent auditors issue them.

Questions

What technology buyers ask before they start.

Anything else? Ask the engineers who would do the work, or plan it first.

First reply
One working day, from an engineer
First call
45 minutes, no slide deck
In confidence
Confidentiality agreement signed first
Outline plan
Scope, shape and a price range within a week

Yes. Start with one: an audit, an AI feature, a website or a team. Each is priced on its own and connects to the rest when you are ready.

Related09Audits01Web & Apps04AI Product

Whichever scores best on your own examples. We use OpenAI, Anthropic, Google, Meta and Mistral models, and open models in your cloud. We pick per task on quality, speed and cost, and switch only when a new model does better.

Related03AI Strategy05AI Infrastructure

Yes. It runs in your AWS, Azure or Google Cloud account, India regions included, with training on your data switched off. Where data cannot leave your network, open models run inside it.

Related05AI Infrastructure06Security

You do: code, AI instructions, test examples and model settings. What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them.

Related02Platforms10Workforce

Early and in writing. We answer your security questions before work starts and follow your policies. The proof auditors ask for comes with the work. Working towards ISO/IEC 27001 or SOC 2? We prepare you for the independent auditor.

Related06Security09Audits

Typically 4–8 weeks from a clear problem to live use. A test version runs on your data within days. A trial with named users starts by week 3. Regulated or high-risk uses take longer to review.

Related03AI Strategy04AI Product06Security

Yes. Engineers can join your team. A dedicated team can own a whole area. Or we coach while your team builds. Handover is planned from week 1.

Related10Workforce07Integration

You choose. We run it with agreed response times, or hand it to your team with guides, dashboards and training. Either way, we review the first 90 days against the agreed measures.

Related07Integration10Workforce

Tell us what you need built.

You will talk to the lead who would run your work.

Book a call

Three ways to start

We always agree a written scope and price before work begins.

Choose one of the three ways above