ContentOps
Content operations: content lifecycle (plan, create, review, publish, maintain, retire), editorial calendars and workflows, content models and structured content, head…
In preparationFree learning library 45 of 100 published
One honest, deeply researched single-page tutorial for each of 100 operations disciplines — from DevOps and SRE to FinOps, MLOps, SecOps and PeopleOps. Every page says what the term really means (and when it is only a label), how the practice works, how to measure it, when not to use it, and where to go next.
New to Ops? The core loop from code to reliable production.
Run infrastructure and internal platforms at scale.
From vulnerabilities to detection and response.
Ship data, models and LLM applications responsibly.
For leaders balancing spend, compliance and risk.
How revenue, customer and people operations fit together.
DevOps is a way of organising software delivery so that the people who build a service and the people who run it share goals, tools and feedback, letting changes reach users quickly, safely and repeatedly. It is judged by delivery outcomes, not job titles.
GitOps is a way of operating software systems in which the desired state is declared in a versioned, immutable store such as Git, and software agents continuously pull it and reconcile the running system to match.
PlatformOps is a less common name for platform engineering. This page uses it for the operating half: running an internal developer platform as a product, with service levels, support, upgrades and deprecation that keep its self-service golden paths trustworthy.
TestOps is the practice of running an automated test suite as a production service: one whose users are developers and whose product is a fast, trustworthy pass/fail verdict on every change. The label is young and vendor-popularised; the practices under it are well established.
DevExOps is a rare, unstandardised label. This page uses it for running developer experience as a continuous loop: measure friction with surveys and system data, prioritise it, get it fixed and verify the fix, without turning the data into surveillance of individuals.
NoOps is the aspiration that automation and fully managed platforms can remove the need for a dedicated operations team. In practice it is a trade-off: operational work shrinks and moves to providers, platforms and developers, but it does not disappear.
ChatOps is the practice of running operational work through shared chat: bots post the events people need and run allow-listed commands on request, so actions, results and the discussion around them are visible, permissioned and auditable.
GitLabOps is this Atlas's name for operating software delivery on the GitLab platform: designing .gitlab-ci.yml pipelines, running runner fleets, governing deployments and scanners, and keeping a GitLab instance healthy and current.
Operating applications in production from the app team's view: you build it you run it, application performance monitoring, app configuration and secrets, health check…
In preparationRunning websites and web apps: web performance (Core Web Vitals), CDNs and caching, TLS/HTTPS, DNS, web servers and reverse proxies (Nginx, Apache), uptime and synthet…
In preparationMobile app delivery operations: mobile CI/CD (Fastlane, Bitrise), code signing and provisioning, app store review and staged rollouts, crash reporting (Crashlytics), m…
In preparationReleaseOps is an informal label for turning deployed code into a deliberate, reversible change for users: versioning, cadence, progressive exposure, feature flags, rollback and release records. The exact name is also a ServiceNow product.
AutomationOps is not a standard term. This Atlas uses it for running operational automation as a governed discipline: choosing what to automate, making it idempotent and safe to repeat, limiting how far one run can reach, and owning it until it is retired.
Workflow orchestration engines and operations: DAGs, state machines, retries and idempotency, long-running and durable workflows, sagas/compensation, Temporal, Apache …
In preparationAPI lifecycle operations: design-first with OpenAPI, API gateways, versioning and deprecation, rate limiting and quotas, API security (OAuth 2.0, keys), contract testi…
In preparationOperating system-to-system integrations: integration patterns (point-to-point, hub-and-spoke, ESB, event-driven), message brokers (Kafka, RabbitMQ), iPaaS, idempotent …
In preparationCloudOps (cloud operations) is running workloads on public cloud through the provider's control plane: account hierarchy, guardrails, quotas, Regions, provider signals and managed-service change. The label is common, but no neutral body defines it.
Network operations centre (NOC) practices: network monitoring (SNMP, NetFlow/sFlow), availability and performance KPIs, network incident and change management, trouble…
In preparationITOps (IT operations) is the function that keeps an organisation's IT services running: it handles requests and incidents, removes the causes of repeat failures, controls changes and keeps an accurate map of the estate, often through ITIL-style ITSM practices.
Database operations: schema migrations as code (Flyway, Liquibase), backups and point-in-time recovery, replication and failover, indexing and query performance, conne…
In preparationKubernetesOps is this Atlas's name for operating Kubernetes clusters and the workloads on them: keeping the control plane, nodes and add-ons healthy and current, making workloads schedule and scale correctly, and diagnosing failures.
SysOps (systems operations) is the hands-on work of keeping servers healthy: services, users and privileges, logs, scheduled jobs, packages, filesystems, time and performance triage. The label is informal; the established practice is system administration.
Storage operations: block vs file vs object storage, RAID, SAN/NAS, cloud storage classes and lifecycle policies, IOPS/throughput/latency, snapshots and replication, c…
In preparationNetwork automation and programmability (NetDevOps): network as code, NETCONF/RESTCONF/YANG, gNMI streaming telemetry, Ansible/Nornir for networks, SDN and intent-based…
In preparationOperating edge computing: edge vs fog vs cloud, constrained and intermittently connected sites, fleet management of edge nodes, K3s/KubeEdge, zero-touch provisioning, …
In preparationIoT device operations: device provisioning and identity, MQTT/CoAP, device shadows/twins, OTA firmware updates, IoT platforms (AWS IoT Core, Azure IoT Hub), telemetry …
In preparationOperating robot fleets: ROS 2 basics (nodes, topics, services), simulation and digital twins (Gazebo), fleet management and remote monitoring, OTA updates for robots, …
In preparationContainerOps is this Atlas's name for operating single containers below the orchestrator: building small, traceable OCI images, managing tags, digests and registries, and running containers predictably on a host's runtime, namespaces and cgroups.
ServerlessOps is the practice of running serverless compute (functions and request-billed containers) in production: owning event retries and duplicates, concurrency, safe deployments and per-invocation cost. The label itself is a niche practitioner term, used mostly between 2016 and 2020.
InfraOps is informal shorthand for infrastructure operations. This Atlas uses it for running infrastructure through code: declaring it, reviewing every change as a plan, applying it from a pipeline and keeping the tool's state in step with reality.
Service operations and service management for digital services: service catalog, service ownership, service level management (SLA/SLO), service maps and dependencies, …
In preparationSite Reliability Engineering (SRE) runs production services as a software-engineering problem: it sets explicit reliability targets (SLOs) from users' experience and uses the remaining error budget to decide how fast to ship and when to stop and fix.
IncidentOps is a rare, informal label for incident management: declaring, coordinating, communicating and learning from unplanned service disruptions. This page teaches that established practice, with a focus on human coordination under pressure.
ObservabilityOps is this Atlas's name for running observability as an internal product: the telemetry pipeline, standards, budgets and alert hygiene that let engineers answer new questions about production at a predictable cost. The label itself is not standardised.
BackupOps is a rare label for backup and recovery operations: keeping independent, protected copies of data and proving with scheduled restore tests that they can be restored recently enough and fast enough for the business.
DisasterRecoveryOps is a rare label for IT disaster recovery run as an operational practice: agreeing how fast each service must return and how much data it may lose, then deciding when to invoke recovery, failing over, failing back and proving it all in drills.
DevSecOps is the practice of building security into the software delivery pipeline and into the teams that run it, so that every change is checked, traceable and safe to ship without a separate security phase that stalls delivery.
SecOps is an ambiguous label. Here it means the working contract between security and IT operations: agreed hardening baselines, one owned remediation queue with deadlines, governed exceptions and joint metrics. Others use it for SOC work or a Google product.
DataSecOps is a vendor-promoted label for building security into data platform operations: classifying data, enforcing who may see which rows and columns, masking or tokenising sensitive fields, and proving it from access logs.
AIOps for Security is the use of statistics, machine learning and language models inside the detect-triage-respond loop of a security operation, evaluated and governed against an adversary: base rates, missed detections, prompt injection and limits on autonomy.
SecDataOps is the engineering and governance of security telemetry: onboarding log sources, parsing and normalising them to a schema, enriching, routing and tiering them, and retaining them so that detections, investigations and audits have complete, trustworthy and affordable evidence.
ComplianceOps runs regulatory and contractual compliance as a continuous operation: one library of controls mapped to every framework in scope, evidence collected and tested on a schedule, exceptions with expiry dates, and audits served from records that already exist.
RiskOps, as this Atlas uses it, is the day-to-day operation of risk decisions: appetite and tolerances, a live risk register, quantification where it pays, and acceptance, treatment or transfer by the owner with the authority, with an expiry. The label has no standard meaning.
In preparationPrivacyOps is a vendor-coined name for running a privacy programme as an operation: knowing which personal data you hold and why, and meeting each person's rights, the impact assessments and breach duties on time, with evidence.
In preparationCloudSecOps is running security for a cloud estate at the provider-API layer: guardrails that block unsafe configuration, continuous posture checks, complete audit logs, and detection and response for control-plane activity. The label is emerging and loosely defined.
KubernetesSecOps is a rare name for Kubernetes security operations: running the controls that decide who may change a cluster, what may run in it, what may talk to what, and how an attack in progress is noticed and contained.
IdentityOps is the day-to-day operation of workforce and machine identities: HR-driven joiner–mover–leaver, directories and identity providers, SSO, SCIM provisioning, phishing-resistant MFA and recovery, and the lifecycle of non-human identities.
IAMOps is an informal label for IAM operations. This Atlas uses it for authorisation as code: designing, testing and evaluating the policies that decide what people, workloads and agents may do, so permissions stay minimal, explainable and testable.
AccessOps is not a standard term. Here it means running the moment of access beyond birthright, above all privileged access: how people request, receive, use and give back access, with no standing admin rights, expiry the system enforces, a tested break-glass path and reviews that can say no.
VulnerabilityOps (usually "VulnOps") runs vulnerability management as a continuous flow: decide what must be fixed by when from exploitation evidence and asset exposure, hand dated work to owners, verify every fix, and keep remediation capacity ahead of arrivals.
ThreatOps is an unstandardised label. This page uses it for running threat intelligence and threat hunting as one operation: priority intelligence requirements steer what is collected and analysed, and testable hypotheses steer hunts whose findings change defences.
SOC Ops is running a security operations centre as a dependable service: turning alerts into timely, recorded decisions through tiers, playbooks, SIEM and SOAR, shift handover, metrics and sourcing choices that people can sustain around the clock.
DetectionOps is a rare label for detection engineering run like software delivery: detections are written as code from threat-informed requirements, tested, peer-reviewed, deployed through a pipeline, measured in production, tuned and retired.
In this Atlas, ResponseOps is security incident response run as an operational capability: contain an active adversary, preserve evidence, evict and recover cleanly, and meet notification duties. The label itself is not a standard term.
PatchOps is an informal name for patch management run as an operation: getting vendor fixes onto every asset through rings, maintenance windows, reboots and rollback, then proving they took effect. The established practice is enterprise patch management.
EndpointOps is an informal name for running user devices through their whole life: enrolment, configuration, compliance, encryption, EDR health, access decisions and retirement, where IT management and security meet. The practice is established as endpoint management plus endpoint security.
AIOps (artificial intelligence for IT operations) applies statistics, machine learning and language models to operational events and telemetry to cut alert noise, group related alerts into incidents, flag anomalies, rank probable causes and run guarded fixes.
MLOps is the engineering practice of getting trained machine-learning models into production and keeping them correct there: versioned data, code and models, automated training and release pipelines, monitoring for skew and drift, and controlled retraining.
LLMOps is the practice of running applications built on large language models in production: versioning prompts, models and retrieval together, gating every change on evaluations, tracing each request, and containing prompt injection, latency and token use.
In preparationDataOps is the practice of delivering and running data pipelines with software discipline: changes are versioned and tested in CI, each load is checked before consumers see it, and data is monitored after, so correct data arrives on time. The label is real but not standardised.
ModelOps is the governance and lifecycle management of every model an organisation relies on (machine learning, rules, optimisation, LLM applications and agents): each one inventoried, risk-tiered, validated, approved for a use, monitored and retired.
In preparationResearchDataOps is this Atlas's name for running research data management as an operational service: planning, describing, identifying, depositing, protecting and preserving research data so that others can find, cite and reuse it for decades.
In preparationAnalyticsOps has no standard definition. On this page it means operating the layer where people consume data: versioned metric definitions, a semantic layer that serves them, and BI content that is certified, monitored and retired, so each important metric has one trusted definition.
In preparationOperationalising decisions: decision intelligence, decision models and DMN, business rules engines, combining rules with ML scores, decision automation with human-in-t…
In preparationKnowledge management operations: KCS (Knowledge-Centered Service), knowledge bases and wikis, tacit vs explicit knowledge, documentation as code, findability and taxon…
In preparationFinOps is the operating model for variable technology spend: engineering, finance, product, procurement and leadership share timely cost data and clear decision rights, so that cloud, SaaS, data-platform and AI spend buys measurable business value.
GreenOps is the practice of measuring and reducing the greenhouse-gas emissions of IT and cloud operations: energy used, the carbon intensity of that energy, and the hardware it needs, reported per unit of work and weighed against cost, latency and reliability.
In preparationCost management of AI/ML and GenAI workloads: GPU/accelerator costs and utilisation, training vs inference cost, token-based pricing, cost per inference/per token unit…
In preparationBusiness operations: strategy-to-execution, OKRs and KPIs, operating cadence (QBRs), cross-functional process improvement, business analytics for decisions, resource p…
In preparationRevenue operations: aligning marketing, sales and customer success, the revenue funnel and lead stages (MQL, SQL), single source of truth in CRM, pipeline and forecast…
In preparationCustomer support operations: ticket triage and routing, tiered support (L1/L2/L3), SLAs (first response, resolution), macros and automation, self-service and deflectio…
In preparationMarketing operations: campaign operations, lead management and scoring, attribution models, marketing automation platforms (Marketo, HubSpot), data hygiene and consent…
In preparationSales operations: territory and quota planning, CRM hygiene (Salesforce, HubSpot), sales process stages, pipeline management and forecasting categories, compensation p…
In preparationCustomer operations and customer success operations: customer lifecycle and onboarding, health scores, churn and retention, NRR/GRR, customer segmentation and coverage…
In preparationCustomer experience operations: customer journey mapping, voice of the customer (VoC) programs, NPS/CSAT/CES, closing the feedback loop, omnichannel experience, moment…
In preparationContent operations: content lifecycle (plan, create, review, publish, maintain, retire), editorial calendars and workflows, content models and structured content, head…
In preparationMedia operations: digital asset management (DAM), media workflows (ingest, transcode, package, deliver), codecs and adaptive bitrate streaming (HLS, DASH), metadata an…
In preparationSEO operations: technical SEO (crawling, indexing, robots.txt, XML sitemaps, canonical tags, structured data), Core Web Vitals impact, keyword research and search inte…
In preparationSEO operations: technical SEO (crawling, indexing, robots.txt, XML sitemaps, canonical tags, structured data), Core Web Vitals impact, keyword research and search inte…
In preparationAdvertising operations: ad servers (Google Ad Manager), programmatic advertising (RTB, SSP, DSP, ad exchanges), campaign trafficking, impressions/CPM/CPC/CTR, viewabil…
In preparationMarketing technology stack operations: stack architecture and integration, CDPs, tag management (Google Tag Manager), first-party data and consent mode, identity resol…
In preparationUX/user research operations: participant recruitment and panels, consent and incentives, research repositories and insight management, research tooling, democratising …
In preparationDesign operations: design systems and tokens, design tooling (Figma) and libraries, design-to-dev handoff, design critiques and reviews, scaling design teams, design w…
In preparationProduct operations: enabling product teams with data, tools and processes, product analytics instrumentation, feedback aggregation, roadmapping cadences, experimentati…
In preparationAgile delivery operations: Agile Manifesto values/principles, Scrum roles and events, Kanban (WIP limits, flow metrics: lead time, cycle time, throughput), scaling fra…
In preparationProject operations/project management: project lifecycle, scope/time/cost triple constraint, WBS, critical path, RAID logs, stakeholder management, earned value basics…
In preparationPortfolio management operations: aligning investments to strategy, prioritisation methods (WSJF, cost of delay, scoring models), capacity-based planning, lean portfoli…
In preparationPeopleOps (people operations) runs an organisation's employee lifecycle (hiring, onboarding, moves, pay, performance and exits) as a reliable, measured operation built on one trusted system of record, clear owners and service levels.
Financial crime operations: AML/CFT, KYC and CDD/EDD, sanctions screening, transaction monitoring and alert investigation, suspicious activity/transaction reporting (S…
In preparationLegal operations: CLOC core competencies, contract lifecycle management (CLM), matter management, e-billing and outside counsel management, legal intake and triage, le…
In preparationProcurement operations: source-to-pay and procure-to-pay processes, purchase requisitions and POs, three-way match, supplier onboarding and management, RFx (RFI/RFP/RF…
In preparationSupply chain operations: plan-source-make-deliver-return (SCOR), demand forecasting and S&OP, inventory management (safety stock, EOQ, reorder point), bullwhip effect,…
In preparationVehicle fleet operations: telematics and GPS tracking, route optimisation, preventive maintenance, fuel management, driver safety and behaviour scoring, utilisation, t…
In preparationRetail operations: store operations, POS systems, omnichannel (BOPIS, ship-from-store), inventory accuracy and shrink, merchandising and planograms, retail KPIs (sales…
In preparationHealthcare operations: patient flow and capacity, EHR systems and interoperability (HL7 v2, FHIR), revenue cycle basics, scheduling and no-shows, clinical operations K…
In preparationBioinformatics and biotech operations: bioinformatics pipelines (Nextflow, Snakemake), workflow reproducibility with containers, sequencing data formats (FASTQ, BAM, V…
In preparationLaboratory operations: LIMS and ELN, sample lifecycle and chain of custody, lab automation and instrument integration, quality systems (GLP, ISO/IEC 17025), equipment …
In preparationOperating financial technology services: payments flows (authorisation, clearing, settlement), payment rails (cards, ACH, UPI, SWIFT), reconciliation, ledgers and doub…
In preparationEducation/learning operations: LMS operations (Moodle, Canvas), course lifecycle and instructional design models (ADDIE), learning standards (SCORM, xAPI, LTI), assess…
In preparationGovernment digital service operations: digital public infrastructure, service standards (e.g
In preparation