Knowledge base
The terms, defined plainly.
A working glossary of the software, AI and infrastructure terms that come up when you are deciding what to build. Written to explain the trade-off, not to sell you the acronym.
21 terms
A
- Agentic WorkflowAI & MLA multi-step process where one or more AI agents carry out a task autonomously, coordinating tools and decisions along the way.
- AI AgentAI & MLAn AI system that takes actions toward a goal (calling tools, querying systems and making decisions), rather than only producing text.
- APIEngineeringAn Application Programming Interface. The defined contract through which one piece of software talks to another.
C
D
E
F
I
K
L
M
- MicroservicesEngineeringAn architecture that splits an application into small, independently deployable services instead of one large codebase.
- Minimum Viable Product (MVP)EngineeringThe smallest version of a product that delivers real value to a user, scoped narrowly so the idea can be tested against real use before the full build.
- MLOpsAI & MLThe practices and tooling for taking machine-learning models to production and keeping them working. The DevOps of ML.
O
P
- Penetration TestingSecurityAn authorised, simulated attack on a system to find the vulnerabilities a real attacker could exploit, before they do.
- Prompt EngineeringAI & MLThe practice of designing the input to a language model to get reliable, correct output, closer to interface design than to trickery.
R
S
T
V
Z
Talking to us means talking to engineers.
No glossary needed on the call. Tell us the problem in your own words and we will translate.
- 01A senior engineer reads it. Not a form queue, and not an account manager.
- 02We reply either with questions or with a straight answer that we are not the right fit.
- 03If it looks like a fit, a technical call with the person who would actually run the delivery.
- 04Then scope, effort and risk in writing, before anyone signs anything.