Skip to content
CODT Technologies logoCODTTECHNOLOGIES
Glossary

Every term we use, defined in plain English.

This glossary defines the software and AI terms that come up in our proposals, services and case studies — from AI agents and RAG to nDSG and WebRTC. Every definition is written to stand on its own, and every entry is grounded in something CODT Technologies has actually shipped, with a link to the service or case study where the term lives in production.

29 terms · A–Z · grounded in shipped work

  • Adaptive bitrate streaming (ABR)

    Adaptive bitrate streaming (ABR) is a video-delivery technique that encodes one stream into a ladder of quality levels and lets each viewer's player switch between them mid-playback, so picture quality tracks the viewer's real bandwidth instead of freezing when the connection dips.

    CODT engineers ABR pipelines as part of its audio and video streaming service — live ingest over RTMP, SRT or WebRTC, adaptive bitrate transcoding, and per-title encoding so a talking-head clip is not billed at the same bitrate as fast-motion sport, with perceived quality validated by VMAF scores rather than by eyeballing it. The approach has held up at real scale: the streaming backbone CODT built for Bizzabo delivers studio-quality live events to 50K+ peak concurrent viewers with stream start under 1.5 seconds, and RushTix's ticketed comedy shows hold a 2.4-second median join time with a rebuffer ratio under 0.4% — numbers that depend on the bitrate ladder being tuned to the actual audience and devices rather than left at a fixed default.

    Explore our streaming platforms service →

  • AI agent

    An AI agent is software that uses a large language model as a reasoning engine to pursue a goal: it breaks the task into steps, calls tools such as APIs, databases and search, observes the results and adjusts — repeating until the job is done or a human needs to step in. Where a chatbot answers questions, an agent takes actions on systems.

    AI agent engineering is a dedicated CODT service. Agents are built with deterministic guardrails — tool-level allowlists, approval gates on sensitive actions, scope-limited credentials — plus a full audit log of every tool call and behavioural eval suites run on every deploy. New agents run alongside humans for four to six weeks before acting unattended, and per-task cost and latency budgets stop runaway loops before they burn money. Across customer-deployed agents CODT reports a mean task completion rate of 92% or higher, with zero unauthorised destructive actions in production. A single-purpose internal agent typically takes four to six weeks to build; a customer-facing agent with multiple tools, approval flows and observability runs ten to sixteen weeks — always starting with a paid one-week scoping spike.

    Explore our AI agents service →

  • AI voice agent

    An AI voice agent is an AI system that holds real telephone conversations — listening, speaking and deciding in real time — so calls that would otherwise queue for a human are answered, qualified or resolved by software.

    CODT built and operates one in production: LeadTrack AI, a multi-tenant voice-agent SaaS engineered end to end for an Australian client — the voice pipeline, telephony integration, per-tenant qualification scripts, intent scoring, tenant isolation and call analytics. The agent phones every new inbound lead in under 30 seconds, while the prospect is still at their screen, holds a natural, interruptible qualifying conversation rather than a phone tree, and routes high-intent prospects to human reps with the full transcript and context attached. The platform has completed more than 100,000 calls in production — the hardening that actually matters for voice agents — and that speed-to-first-call mechanism produced a +38% conversion lift. The whole system runs with data resident in AWS Sydney.

    Read the LeadTrack AI case study →

  • Answer engine optimisation (AEO)

    Answer engine optimisation (AEO) is the practice of structuring web content so AI answer engines — ChatGPT, Perplexity, Google's AI Overviews — can extract, cite and accurately reproduce it when users ask questions, rather than merely ranking it in a list of blue links.

    AEO is built into CODT's web app development service rather than sold as a separate trick: Schema.org structured data (Organization, FAQ, Article, Breadcrumb), clear question-led headings and clean semantic HTML give answer engines something reliable to lift, and the same technical foundation is what serves classic SEO — sites ship with a Lighthouse SEO score of 100 and Core Web Vitals of 90 or better. CODT applies the discipline to its own site: service pages open with liftable definition paragraphs, FAQ answers are rendered fully in the server-side HTML rather than mounted on click, and structured data mirrors the visible content — the same pattern this glossary follows, where every entry leads with a quotable definition sentence an answer engine can cite.

    Explore our web development service →

  • Buddy-punching

    Buddy-punching is a form of time theft in which one employee clocks in or out on behalf of an absent colleague, inflating recorded hours and quietly corrupting the payroll data a business pays out against.

    CODT engineered this problem away for FeelEat, a Swiss food operator, with TapTime — an attendance app whose clock-ins are bound to the site and the person: NFC taps on site-mounted tags, QR scans and biometric confirmation, flowing straight into the ERP that runs payroll. Device binding and verification make clocking a colleague in structurally impractical rather than merely forbidden, and because a verified clock-in takes about a second, the honest path stays the easy one. Across FeelEat's kitchens, logistics and retail sites the results were immediate: buddy-punching dropped by about 95%, attendance accuracy reached 99.5%, and payroll preparation became roughly 80% faster because verified hours no longer needed re-keying — or arguing over. The same verified record feeds FeelEat's companion employees app, where payroll accuracy sits at 99.8%.

    Read the TapTime case study →

  • Core Web Vitals

    Core Web Vitals are Google's user-experience metrics for web pages — how fast the main content paints (Largest Contentful Paint), how quickly the page responds to interaction, and how much the layout shifts while loading (Cumulative Layout Shift) — and they influence search ranking as well as user patience.

    CODT's web development service treats the vitals as an engineering budget, not a post-launch fix: LCP under 2.5 seconds and CLS under 0.1 are targeted from the first build and checked on every pull request in CI rather than audited at the end. The discipline is deliberately unglamorous — images served in AVIF/WebP at correct sizes with explicit dimensions, non-critical JavaScript deferred, fonts self-hosted with font-display swap, below-the-fold content lazy-loaded — and framework choice matters too: Astro for content-heavy sites that should ship almost no JavaScript, Next.js where real interactivity earns its weight. Sites ship with Lighthouse Performance at 90 or above and a Lighthouse SEO score of 100, and relaunches have averaged a +60% organic traffic lift within 90 days.

    Explore our web development service →

  • CRM (customer relationship management)

    A CRM (customer relationship management) system is the software of record for a company's prospects and customers — contacts, deals, conversations and pipeline — so that sales and support teams work from one shared history instead of private inboxes and memory.

    CODT builds around CRMs rather than replacing them. The ERP and business automation service ships production integrations with Salesforce and HubSpot alongside accounting platforms — two-way sync with stable external ID mappings, idempotent updates, a clear system-of-record per field so conflicts resolve deterministically, and reconciliation reports that surface anything that didn't match. On the AI side, CRM integration is where a voice agent earns its keep: LeadTrack AI, the multi-tenant calling platform CODT engineered, routes qualified leads to human reps with the full call transcript and intent score attached. And because CODT builds each agent per engagement rather than selling a fixed product, CRM and telephony integrations are scoped against the client's actual stack during discovery — not against a generic connector list.

    Explore our business automation service →

  • Data residency

    Data residency is the requirement that data be stored and processed within a specific geographic jurisdiction, making the physical location of your servers a legal and contractual matter rather than a purely technical choice.

    CODT treats residency as an architecture decision made at the start of an engagement, not an afterthought: EU or Swiss data residency is available on request for European clients, whose engagements are GDPR- and nDSG-aware by default, and UAE work is designed with the PDPL in view. The claim is not hypothetical — CODT already runs residency in production: LeadTrack AI, the voice-agent SaaS built for an Australian client, operates with data resident in AWS Sydney, designed against the Privacy Act 1988 and the Australian Privacy Principles. The Trust Center lists data residency alongside NDAs as standard on-request terms, and CODT's cost guides name audit-trail and data-residency requirements as items scoped into the fixed quote during the discovery sprint — before the build, not after an audit finds the gap.

    Visit the Trust Center →

  • Demand forecasting

    Demand forecasting is the use of statistical or machine-learning models to predict future demand from sales history, seasonality and live operational signals, so that inventory, staffing and purchasing are planned against a number instead of a guess.

    CODT built a demand-forecasting platform for the FeelEat group that runs at 98% accuracy in production — measured continuously against what actually sold, not a one-off holdout result. Models were trained on two years of sales history plus seasonality, calendar effects and weather, forecasting per site and per dish — the granularity at which ordering decisions are actually made. Both directions of error shrank: stockouts fell 58% and excess stock fell 41%, and the platform paid for itself in the first quarter. The rollout is as instructive as the math: the model ran in shadow mode next to human plans until its track record won the argument, then cut over site by site — and the model itself took weeks, while the data plumbing, drift monitoring and the 8 a.m. planning views took months.

    Read the forecasting case study →

  • Design system

    A design system is a product team's single source of truth for interface decisions — design tokens for colour, type and spacing, a documented component library, and usage rules — so screens stay consistent as the product and the team grow. A UI kit is a folder of styled components; a design system adds the rules that keep it coherent.

    CODT's UI/UX design service delivers design systems built to survive contact with code: tokens are handed off implemented in Tailwind and CSS variables, the component library is mirrored in Storybook so designers and engineers work from one source of truth, and accessibility is designed in to WCAG 2.2 AA — colour contrast, keyboard navigation, screen-reader labelling, focus states — rather than bolted on after launch. Designers stay involved through the build to review the implementation and defend the work in code, because handoff is a process, not a wall to throw files over. The results are measured where they matter: a median post-launch usability task success rate above 95% across shipped designs.

    Explore our UI/UX design service →

  • Discovery sprint

    A discovery sprint is a short, fixed-fee scoping engagement — typically one to two weeks — in which a senior team maps a software project before any build begins, ending in a written scope and a priced proposal rather than an open-ended estimate.

    Every CODT engagement opens with one, led by a senior architect rather than a salesperson. The deliverable is concrete: a written scope document, a clickable prototype of the riskiest flows, an architecture sketch with key decisions recorded as ADRs, a fixed and transparent quote, and an explicit "won't build" list. Nothing moves forward until that document is signed — and it is a real artefact the client owns, so taking it to another firm to build is a legitimate outcome. The sprint is also where the numbers get honest: CODT publishes no cost ranges, because the discovery sprint is what turns a guess into a scoped, fixed price — with integrations, compliance requirements and the v1 cut-line named before the quote rather than discovered after it.

    Read the app cost guide →

  • Edge computing (IoT edge)

    Edge computing runs processing on or near the device that generates the data — an embedded board, a gateway, an in-store machine — instead of shipping everything to a distant cloud, which cuts latency, bandwidth cost and the fragility of depending on a connection. In IoT systems this is often called the IoT edge.

    CODT's IoT solutions service designs hybrid edge-cloud architectures as the default: the edge filters, the cloud decides. Inference and filtering move onto devices — anomaly detection running on an NVIDIA Jetson rather than streaming raw video upstream — when bandwidth is expensive, latency matters or the device must keep working offline; cross-fleet aggregation and heavy models stay in the cloud. Intermittent connectivity is treated as the normal case, not the exception: devices buffer readings locally and replay them with timestamps preserved on reconnect, and critical control logic runs locally so hardware degrades gracefully when the link drops rather than failing. In deployed fleets, median end-to-end latency from device to dashboard is under 800 milliseconds.

    Explore our IoT solutions service →

  • ERP (enterprise resource planning)

    An ERP (enterprise resource planning) system is the internal platform a company runs its operations on — orders, inventory, finance, HR and workforce in one auditable system of record — replacing the spreadsheets, email threads and disconnected tools that growth otherwise accumulates.

    CODT builds purpose-fit ERPs for companies whose growth is outpacing their tooling, rolling out module by module alongside the legacy process rather than big-bang. The longest-running proof is FeelEat's ERP portal, which runs the Swiss food operator's back office across 200+ corporate clients: orders, staff schedules, employee records, vouchers and event bookings in one login. It saves around 12 hours per staff member per week, and sales reconciliation that took two days now completes in roughly four hours. The same spine carries the workforce layer — TapTime's verified clock-ins sync into it in real time, which is what made payroll preparation roughly 80% faster. Where standard ERPs fit (NetSuite, SAP, Odoo), CODT says so; custom is for workflows the packages can't model without permanent technical debt.

    Read the ERP Portal case study →

  • Fixed-price engagement

    A fixed-price engagement is a software contract in which the cost is agreed in writing before the build starts, moving delivery risk from the client's budget onto the vendor's scoping discipline.

    CODT quotes fixed prices deliberately — and is explicit about where the model's limits are. Every engagement is priced once the scope is known: a paid discovery sprint produces a fixed, transparent quote in writing before any build begins, and no public cost ranges are published, because a number quoted before scope is known prices the guess rather than the work. The honesty runs both ways: for open-ended, months-long product builds, CODT states plainly that pretending to fix-price evolving requirements just incentivises corner-cutting, so those run time-and-materials against a banded estimate with quarterly re-forecasting. What stays fixed is the discovery sprint itself and any well-defined slice — and the hire pages put the billing philosophy simply: by outcome, not by the hour, with no open-ended hourly billing.

    Read the app cost guide →

  • Follow-the-sun development

    Follow-the-sun development is a delivery model in which teams distributed across time zones hand work to one another around the clock, so a project keeps moving while any one office sleeps.

    CODT runs this model structurally: the engineering hub is in Gurugram, India, a North American office sits in Milpitas, California, and client-facing business contacts for European work are based in Switzerland. Stand-ups and demos happen on the client's clock, and collaboration runs in English, French and German. The arrangement is not an outsourcing veneer — the firm describes it as Swiss points of contact with senior global engineering across Silicon Valley and Gurugram — and it is how a company founded in Gurugram in 2017 came to serve clients in 10+ countries, with long-tenure engagements like FeelEat in Switzerland running for nine-plus years and LeadTrack AI delivered for an Australian client with data resident in AWS Sydney. Whatever the time zone, a senior engineer replies to enquiries within one business day.

    See the dedicated team model →

  • GDPR

    The GDPR (General Data Protection Regulation) is the European Union's data-protection law, governing how organisations collect, process, store and delete the personal data of people in the EU — and its obligations reach any company serving European users, wherever that company is based.

    CODT's wording on GDPR is deliberately precise: engagements are GDPR-aware by default — privacy-first architecture as the engineering default from the first commit, not a compliance add-on and never a claimed certification. EU data residency is available on request, and the firm has built this way for European clients for nearly a decade, including nine-plus years running FeelEat's Swiss platform. Jurisdiction-specific laws are layered on the same baseline rather than treated as exceptions: Swiss engagements are nDSG-aware, UAE work is designed with the PDPL in view, and Australian builds are designed against the Privacy Act 1988 and the APPs. The Trust Center documents each of these claims at awareness level — its stated rule is that a claim that cannot be verified is not made.

    Visit the Trust Center →

  • hreflang

    hreflang is an HTML attribute that tells search engines which language and regional versions of a page exist, so a French-speaking searcher lands on the French page instead of a duplicate-looking English one — without it, multilingual sites compete against themselves in search.

    Internationalisation, hreflang and locale-based routing are standard features of CODT's web development service: multilingual builds get a CMS structure where translators work per-locale without breaking the layout, hreflang tags so Google serves the right language, and the honest advice that machine-translated content underperforms — the technical i18n plumbing is CODT's job; quality translation is the client's or a partner's. CODT practises this on its own site: codttech.com is served in English, French and German with locale-based routing and hreflang alternates on every translated page, while single-language pages — like this glossary — declare only English, so the other locales never claim translations that don't exist. The same technical-SEO foundation — semantic HTML, structured data, sitemap, robots and hreflang — ships with every build.

    Explore our web development service →

  • Human-in-the-loop

    Human-in-the-loop is an automation design pattern in which an AI system executes routine steps autonomously but routes consequential decisions — irreversible, financial or customer-facing actions — to a person for approval before acting.

    In CODT's AI agent engagements the pattern is a risk-tiering exercise, not a philosophy: during scoping, every action an agent can take is tiered by blast radius, and approval gates land only on the irreversible or high-consequence ones — sending money, deleting data, emailing a customer — so a human reviews roughly 5% of steps rather than 95% and the agent stays useful. The gate UI shows the agent's reasoning and the exact proposed action, so approval takes seconds rather than requiring an investigation. New agents also run alongside humans for four to six weeks before acting unattended, and when a cost or step budget trips, the agent escalates to a human instead of failing silently. The production record this discipline protects: zero unauthorised destructive actions across deployed agents.

    Explore our AI agents service →

  • Multi-tenant SaaS

    A multi-tenant SaaS platform serves many customer organisations — "tenants" — from one codebase and one infrastructure, with each tenant's data, users and configuration strictly isolated from every other's; it is the architecture behind most modern subscription software.

    Multi-tenancy is the core of CODT's SaaS app development service: the default is a single-database, row-level-security model with strict tenant_id propagation through every query, backed by an integration test suite that fails any cross-tenant read, and tenant isolation verified by third-party penetration test. Enterprise contracts needing physical separation get a per-tenant schema or per-tenant database tier. The pattern runs throughout CODT's shipped work: LeadTrack AI is a multi-tenant voice-agent SaaS where every customer operates their own agents, scripts and pipelines on one codebase, and Aviatize serves aviation operators worldwide on isolated tenants of a single platform managing 1,000+ aircraft. The same architecture powers the white-label model, where partners resell a shared platform under their own brand with per-tenant configuration and no code changes.

    Explore our SaaS development service →

  • MVP (minimum viable product)

    An MVP (minimum viable product) is the smallest version of a product that can be put in front of real users to test whether it is worth building further — a deliberately drawn cut-line, not a rough draft of everything.

    CODT's mobile app development service quotes a focused MVP at 10–14 weeks from kickoff to store submission, with enterprise-grade products running four to seven months — and shares a fixed-scope estimate only after the discovery sprint, so the number is grounded in the actual app rather than a template. The firm's cost guides argue the cut-line is the single biggest budget lever: deciding what a chargeable first version must do, and what can honestly wait, moves the cost more than any technology choice — which is why drawing that line is the main job of the discovery sprint. Delivery then proceeds in vertical slices, shipping end-to-end functionality (UI to API to database to telemetry) rather than half-built layers, so the MVP is production-quality from day one instead of a prototype pretending otherwise.

    Explore our mobile development service →

  • nDSG (Swiss Federal Act on Data Protection)

    The nDSG (neues Datenschutzgesetz) is Switzerland's revised Federal Act on Data Protection, in force since September 2023 — Swiss privacy law modernised along lines broadly aligned with, but legally distinct from, the EU's GDPR.

    Switzerland is a core market for CODT — the firm's business-development contacts are based there, client communication runs in German, French or English, and its longest engagement is FeelEat, a Swiss foodtech operator whose platform CODT has built continuously for nine-plus years. Accordingly, every Swiss engagement is GDPR- and nDSG-aware by default: privacy-first architecture from the first commit rather than a compliance retrofit, with EU or Swiss data residency available on request. The distinction matters for Swiss buyers because the nDSG is not the GDPR — a Swiss company can owe duties under both — so CODT names both in its delivery baseline rather than assuming EU alignment covers Switzerland automatically. The Switzerland hub page and the Trust Center document the claim in the same careful, awareness-level language.

    See our Switzerland hub →

  • OTA (over-the-air) updates

    An over-the-air (OTA) update delivers new firmware or software to devices remotely — no technician, no cable — and is the only practical way to maintain a fleet of hardware deployed across many physical sites.

    CODT's IoT service treats the OTA pipeline as safety-critical engineering: updates roll out staged (5% → 25% → 100%) with automatic rollback on failure metrics, dual-bank firmware so a failed update can never brick a device, and signed images so unauthorised firmware cannot load. Device identity is provisioned at manufacturing time, so each unit authenticates on first power-up with no manual setup. The measured result across deployed fleets is an OTA success rate of 99.5% or better. The pattern runs live in FeelEat's Happy Fridge network, where every connected fridge streams stock, temperature and health telemetry into operations and receives over-the-air updates across the fleet — failures are fixed remotely before perishable stock spoils, which is what lets an unmanned-retail business operate 24/7 without staff on site, nine-plus years and counting.

    Explore our IoT solutions service →

  • RAG (retrieval-augmented generation)

    Retrieval-augmented generation (RAG) grounds a large language model's answers in your own documents: at question time, relevant passages are retrieved from a knowledge base and handed to the model as context, so responses draw on real sources instead of the model's memory — the standard cure for hallucinated answers.

    RAG is a first-class capability in CODT's AI/ML solutions service, and the firm's engineering position is that retrieval quality is mostly an ingestion and chunking problem, not an embedding-model problem: documents are chunked semantically rather than by fixed token windows, metadata filters are added, and hybrid search (BM25 plus dense vectors) runs behind a reranker — with recall@k measured on a labelled set before anything gets tuned. Vector databases (pgvector, Pinecone, Weaviate) are chosen per engagement. RAG also anchors CODT's stance on hallucinations — retrieval grounding, citation requirements and structured outputs are system-design mitigations, backed by eval harnesses that fail builds when factuality regresses — and its honest advice on fine-tuning: for factual knowledge, retrieval almost always beats fine-tuning, because fine-tuning teaches behaviour, not facts.

    Explore our AI/ML solutions service →

  • Self-service kiosk

    A self-service kiosk is a fixed touch-screen terminal where customers browse, order and pay without staff — the retail pattern that removes the queue by removing the counter, from fast-food ordering to unmanned stores.

    CODT built the self-service kiosk in FeelEat's smart-fridge ecosystem: a tablet interface where customers scan, browse and buy in seconds, sharing one live inventory with the fridges and the mobile app so what the screen shows is what is actually inside. It runs unattended in production at 99.7% uptime with 99.4% payment success, and the median order completes in 42 seconds — fast enough that lunch queues simply don't form. Kiosk software is also one of the pre-built foundations in CODT's white-label catalogue, so operators can launch a branded kiosk product in weeks rather than quarters. Together with the connected fridges, the kiosk forms the retail edge of the wider unmanned-retail loop that has run in Switzerland for nine-plus years.

    Read the Smart Kiosk case study →

  • Smart-fridge vending (unmanned retail)

    Smart-fridge vending is unmanned retail through a connected fridge that identifies the customer before the door opens, tracks what leaves each shelf and charges automatically when the door closes — a shop with no staff, open around the clock.

    CODT engineered the category end to end for FeelEat in Switzerland: the Happy Fridge platform — connected fridges, the scan-to-unlock flow, in-app payment, live inventory telemetry and the menu experience, with nutrition, allergens and ingredient origins visible per dish. The closed loop is the business model: because the door only opens for a known, payable customer and the sale settles itself on door close, there is no checkout step to skip, and theft dropped roughly 90% compared with honour-system fridges. The platform has run for more than nine years with the same team shipping every release, reaching 40K+ app downloads and supporting a business now valued at $10M+ — proof that unmanned retail holds as an operating model, not just as a demo.

    Read the Happy Fridge case study →

  • SOC 2

    SOC 2 is an assurance framework in which an independent auditor attests to a company's controls for security, availability and confidentiality — Type I at a point in time, Type II over an observation period — and enterprise buyers increasingly require it from SaaS vendors before signing.

    SOC 2 readiness is a named path in CODT's SaaS app development service: the firm has led several SOC 2 Type II readiness engagements, partnering with auditors like Vanta and Drata, and typically reaches Type II in six to nine months from kickoff — the technical lift is real but manageable when the platform is built for it. The engineering foundations that make an audit survivable are defaults in CODT's SaaS builds rather than retrofits: role-based access control with audit logs, tenant isolation verified by penetration test, secrets in a dedicated manager with rotation, and least-privilege IAM with short-lived credentials. Compliance readiness — SOC 2, GDPR or HIPAA depending on the industry — is scoped explicitly in the discovery sprint, so the requirement lands in the architecture rather than in a post-audit rebuild.

    Explore our SaaS development service →

  • Tenant isolation

    Tenant isolation is the architectural guarantee that no customer of a shared software platform can read or affect another customer's data — enforced in the database and query layer, not just promised in the contract.

    CODT's default isolation model for SaaS builds is single-database row-level security with strict tenant_id propagation through every query — backed by an integration test suite that fails any cross-tenant read, so a regression cannot ship silently, and verified from the outside by third-party penetration test. Enterprise contracts that require physical separation get a per-tenant schema or per-tenant database tier instead. The guarantee carries CODT's production platforms: Aviatize serves flight schools, clubs and commercial operators worldwide on isolated tenants of one codebase, managing 1,000+ aircraft with audit-shaped reporting; LeadTrack AI keeps every customer's agents, scripts and pipelines isolated on a shared voice platform across 100K+ calls; and the white-label model depends on it, since each reseller's customers get isolated tenants under one brand.

    Read the Aviatize case study →

  • WebRTC

    WebRTC (Web Real-Time Communication) is the open standard that lets browsers and apps exchange audio and video with sub-second latency — the technology behind in-browser calls and truly interactive live streams, where even a few seconds of delay would break the experience.

    In CODT's streaming engagements, WebRTC is a deliberate tool rather than a default. The service's ingest guidance: RTMP remains the universal encoder-friendly baseline, SRT covers contribution over unreliable networks, and WebRTC is reached for when the use case genuinely needs conversational latency — interactive auctions, betting, two-way shows — because it is materially harder to scale. On the delivery side the same logic applies: standard HLS sits at 15–30 seconds, Low-Latency HLS gets to 2–5, and WebRTC goes sub-second, with cost and buffer resilience trading off at every step down. WebRTC appears in the shipped stacks of both Bizzabo's event streaming backbone — 50K+ peak concurrent viewers, sub-1.5-second stream starts — and RushTix's live comedy platform, where a 2.4-second median join and sub-0.4% rebuffer ratio keep the crowd laughing together.

    Explore our streaming platforms service →

  • White-label software

    White-label software is a proven product built by one company and rebranded by another to sell as its own — the buyer gets speed and a hardened codebase; the end customer sees only the buyer's brand.

    White-label is a distinct CODT offering with a published catalogue: self-service kiosk software, employee clock-in, telemedicine patient portals and food-tech ordering, each re-brandable end to end — colours, typography, logos, copy, locale, currency — with app-store submission under the partner's brand. Median time to launch is six weeks (typically four to eight), at roughly 30–60% of the cost of an equivalent bespoke build, because the engine's maintenance cost is shared across every partner on the platform. Two ownership routes are offered up front: a licence model, where core upgrades and security patches keep flowing to all tenants, or a full source-code transfer. And every engagement includes a fork path — if the business outgrows the shared foundation, CODT takes a clean fork and evolves it as a bespoke build, with no platform-lock-in penalty.

    Explore our white-label service →
Keep exploring
AI agent developmentThe FeelEat ecosystemLeadTrack AI case studyApp development cost guideSwitzerland hubTrust Center
Ready to build

Have a problem worth
solving well?

Tell us about your product, your timeline, and your constraints. We will reply within one business day with an honest read on fit, scope, and the right team to put on it.

Book an intro callEmail us directly