Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
What Is RAG
Definition Retrieval-augmented generation (RAG) is a technique that improves the accuracy and relevance of AI-generated responses by first retrieving relevant information from a knowledge base and then using that information as context when generating an answer. Instead of relying solely on what the language model learned during training — which may be outdated or too general — RAG fetches specific,...
What Is React
Definition React is an open-source JavaScript library, originally created by Facebook (now Meta), for building user interfaces. It allows developers to create web applications where the page updates dynamically without needing a full reload every time the user clicks something. React works by breaking the interface into small, reusable pieces called components — a navigation bar, a search box, a...
What Is React Native
Definition React Native is an open-source framework created by Meta (formerly Facebook) for building mobile applications that run natively on both iOS and Android from a single codebase. It uses the same component-based approach as React (the web library), but instead of rendering to a web browser, it renders to native mobile interface elements — real iOS buttons, real Android...
What Is Redis
Definition Redis is an open-source, in-memory data store that keeps frequently accessed data in your server’s RAM rather than on disk. Because RAM is orders of magnitude faster than disk storage, Redis can read and write data in microseconds. It is most commonly used for caching (storing pre-computed results), managing user sessions, powering real-time features like live notifications, and handling...
What Is Refactoring
Definition Refactoring is the process of restructuring existing code to make it cleaner, more efficient, or easier to maintain, without changing what it actually does from the user’s perspective. The software behaves exactly the same before and after — the improvements are internal. It is comparable to reorganising a warehouse: the same products are stored and shipped, but the layout...
What Is a Repository
Definition A repository (often shortened to “repo”) is the central location where all the files, version history, and changes for a software project are stored. Think of it as a project folder with a built-in memory — it records every change ever made, who made it, and when. Repositories are typically hosted on platforms like GitHub or Bitbucket, which add...
What Is Responsive Design
Definition Responsive design is an approach to building websites and applications so they automatically adjust their layout to fit any screen size — from a large desktop monitor to a tablet to a mobile phone. Rather than building separate versions for different devices, a responsively designed site uses flexible grids, scalable images, and layout rules that adapt based on the...
What Is a REST API
Definition A REST API (Representational State Transfer API) is a specific style of API that uses standard web protocols to send and receive data. It works over the same technology as regular web browsing — URLs and HTTP requests — which makes it the most widely used approach for connecting web applications, mobile apps, and business systems. When a developer...
What Is a Retainer
Definition A retainer is a recurring arrangement where a client pays a fixed amount on a regular basis — usually monthly — in exchange for ongoing access to services. Rather than commissioning work project by project, the client secures a set allocation of time, support, or expertise. In the context of digital agencies and software companies, retainers typically cover ongoing...
What Is a Reverse Proxy
Definition A reverse proxy is a server that sits between your website visitors and your actual web server. When someone visits your site, their request goes to the reverse proxy first, which then forwards it to the appropriate backend server, receives the response, and sends it back to the visitor. The visitor never communicates directly with your backend. This intermediary...
What Is Robotic Process Automation
Definition Robotic Process Automation (RPA) is the use of software bots to carry out repetitive, rule-based tasks that a person would normally do on a computer. These bots can click buttons, copy data between systems, fill in forms, send emails, and follow predefined workflows — all without human intervention. Despite the name, there are no physical robots involved. The “robot”...
What Is robots.txt
Definition robots.txt is a small text file that sits at the root of your website and gives instructions to search engine bots about which pages or sections of your site they are allowed to crawl. It acts as a set of ground rules — you can use it to block bots from accessing areas that are not useful in search...
What Is ROI
Definition ROI stands for Return on Investment — it is a measure of how much value you gain relative to how much you spend. In its simplest form, ROI compares the benefit of an investment to its cost. If you spend ten thousand pounds on a system that saves you twenty thousand pounds per year in manual work, the ROI...
What Is Role-Based Access Control
Definition Role-Based Access Control (RBAC) is a method of managing what users can see and do within a system by assigning them to roles, where each role has a defined set of permissions. Instead of configuring access for every individual user, you create roles — such as Admin, Manager, Editor, or Viewer — and assign the appropriate permissions to each...
What Is a Route
Definition A route is a rule that maps a web address to a specific action inside an application. When someone visits a URL or a system sends a request, the application checks its list of routes to determine what should happen. Routes connect the address someone is requesting — like “/projects” or “/invoices/123” — to the piece of code that...
About the Glossary
Why Plain Language Matters More Than Technical Fluency
Every software project involves terminology that business owners are expected to understand but rarely have reason to learn. Developers use terms like API, CI/CD, middleware, and bearer token as if everyone shares the same vocabulary — and when a client nods along without fully understanding, decisions get made on incomplete information. That gap between technical language and business understanding is where the most expensive mistakes happen: approving architectures you cannot evaluate, signing off on testing strategies you cannot verify, and accepting timelines based on concepts you have not had properly explained.
This glossary exists to close that gap. Each entry provides a plain-English definition, an explanation of why the term matters to your business, and a concrete example of the concept in action. These are not textbook definitions written for computer science students. They are practical explanations for the person who needs to make decisions about software without becoming a developer in the process.
We built this glossary from the questions our clients actually ask — in discovery calls, during project reviews, and in Slack threads where someone finally admits they are not sure what a term means. The entries reflect what business owners genuinely need to understand, not what a technical writer thinks is important. Across hundreds of client engagements, we have found that the single biggest predictor of a smooth project is a client who understands enough vocabulary to ask the right questions. Not to write the code — just to evaluate the answers they are given.
The definitions here deliberately link to deeper content elsewhere on the site. If a glossary entry sparks a question about how we implement something, the Knowledge Center, Services, and Systems sections have the full picture. The glossary is the starting point, not the destination.
Need a Term Explained?
If you have come across a term we have not covered yet, let us know and we will add it.