Account consolidation Merging two or more cloud accounts of similar purpose into one when maintenance overhead exceeds the isolation benefit, compliance allows it, or an account is forgotten with low… 1 Account filter A platform engineer scoped to team=platform sees their team's resources across the 3 accounts that hold platform infrastructure. They can further filter to "just… 1 Account isolation Separating production, non-production, and compliance-scoped workloads into distinct cloud accounts so that a breach, misconfiguration, or runaway script in one account cannot… 1 Account split Dividing one cloud account's resources across multiple accounts when the account grows too large for cloud quotas, blast radius grows too big, distinct teams emerge, or compliance… 1 Action default The conservative predefined action ZopNight recommends per rule category (for example Terminate with snapshot for idle, Downsize during maintenance for rightsizing, Attach to… 1 Action item tracking The formal tracking of postmortem action items, where each item has a single owner, a specific deliverable, a due date, a status of open, in-progress, done, or cancelled, and a… 1 Action status - Resources page, single resource: click row → Stop / Start button - Bulk selection, checkbox + sticky banner → Stop selected / Start selected - Action status panel, appears at… 1 Actionable visibility Inform is the first phase of the FinOps lifecycle. It answers the question: who knows what about cloud spend, when, in what form, and with what action available? Most FinOps… 1 Active-active vs warm standby Two disaster-recovery tiers, where active-active keeps synchronous multi-region writes with RTO under one minute and RPO of zero, while warm standby keeps a secondary replica… 1 Activity-sync The Recent Activity tab in the evidence panel shows operations against the resource, pulled from CloudTrail (AWS) / Cloud Logging (GCP) / Azure Activity Log via the daily… 1 ActualCost Azure's Cost Management API exposes two cost columns: ActualCost and AmortizedCost. 1 Adaptive batching Anomaly detection that scales its batch size to organization resource count (25 at 5,000 resources or fewer, 5 at 20,000 or fewer, and 1 at a time above 20,000) so larger estates… 1 Admin ZopNight ships with four system roles: Viewer, Editor, Admin, and SuperAdmin (default_roles.go), designed to cover the common 80% of role assignments without custom-role work.… 1 Adopt flow A 10-minute exercise reveals the adopt flow's safety. 1 Adopt-or-promote The one-way transition where editing an adopted, observation-only autoscaler policy automatically promotes it to a recommended, ZopNight-managed policy, so adopted policies should… 1 Adopt-or-replace Pattern where ZopNight detects existing cloud scaling and asks the user whether to adopt (observe) or replace (manage). 1 Advanced mode Quick Setup is a streamlined flow for the most common autoscaler scenario: pick a target, accept smart defaults, save. Three clicks. For Advanced cases (custom metrics,… 1 AES-256-GCM Encryption used for credential storage. 1 Agent-friendly workflow Work that fits an agent's strengths because it is multi-step, multi-source, produces written output, requires non-trivial synthesis, and repeats often enough to be worth saving as… 1 Agent-helps-human-writes loop The operating pattern where an agent investigates via read-only MCP tools and recommends an action with justification, but a human reviews and executes the change through the… 1 AI bolt-on For competitive conversations, ask: "Is their AI bolt-on or MCP-native? Read-only or write-capable?" The answer determines whether they're a real competitor on AI specifically. 1 Alert fatigue Severity tuning is iterative. A team that sees too many WARNINGs and starts ignoring them is paying alert fatigue cost. The fix is to downgrade events that are informational,… 4× Allocation These are not synonyms. Showback and chargeback differ in whether money actually moves. Allocation is the math underneath either of them. 1 Allocation dimension The primary axis (Organisation, Teams, or Tags) along which showback and chargeback cost is grouped and presented in Reports, each with its own sweet spot. 1 Allocation rule A documented policy specifying how a shared or indirect cost is distributed across teams or cost centers, recording what it allocates, why, how (formula or fixed percentage), when… 1 Allocation rule audit A quarterly review that retires allocation rules unused for six or more months or with under $100 per month of impact, targeting a roughly 10 percent reduction in rule count per… 1 allResources flag The RBAC field that, when true, lets a user act on all resources in the org, and when false restricts the user to the specific set defined by their resourceIds list. 2× Always-on exception A resource explicitly run 24/7 even in non-production because business need justifies it, such as office-hours-only B2B SaaS or regional shutdowns where no customers exist in that… 1 Amortized cost The cost of an upfront commitment (RI, Savings Plan, CUD) spread across the hours it covers, so each resource shows its true effective daily cost. Not Azure-specific: AWS exposes… 2× Annotation In forecasting, a documented note attached to a projection that records the assumptions, drivers, and risks behind it, such as a planned feature launch, an assumed growth rate, or… 1 Annual account review Annual account review (2-3 weeks of focused work). Plan migrations with clear ROI. Production never consolidates; non-prod flexes. 1 Annual freeze calendar Most pitfalls are process gaps. The annual freeze calendar + communication checklist prevent most. 1 Annual run-rate The projection of savings across a full 12 months extrapolated from realized short-term savings, for example scaling roughly $4,800 of weekly savings into a $250K annual figure… 1 Anomaly When a cost anomaly fires, the first 15 minutes determine whether it becomes an incident (cost overrun, requires response) or stays an event (recorded, no action). The same… 1 Anomaly detection Daily cron detecting cost deviations across 5 dimensions. 1 Anomaly dimension One of the five levels (org, cloud account, resource group, resource, and team) across which ZopNight detects cost anomalies, each catching a different kind of event and used as a… 1 Anomaly severity bands Three anomaly severity bands. Each has a recommended response, notification routing, and SLA. 1 Anomaly signature The Anomaly drawer in ZopNight surfaces a suggested cause based on the anomaly signature: 1 Anti-pattern For each anti-pattern, the fix is structural change, not exhortation: 2× API request charge A per-call cloud bill line item for services that bill by request volume rather than running time, such as Lambda invocations, S3 GET, PUT, and LIST, and DynamoDB capacity units,… 1 API-driven schedule A schedule started and stopped by API calls from a test pipeline rather than a fixed cron, typically paired with a backup schedule that force-stops the environment if the pipeline… 1 App Registration Azure uses Azure AD applications with service principals as the runtime identity. ZopNight asks for an app registration with two roles: 1 Apply / dismiss / snooze Recommendations is the canonical triage surface. Pair with weekly Operate meeting. Document apply / dismiss / snooze in #finops-weekly. 1 Approval decline rate The share of approval requests that are declined, where a near-zero rate under 5 percent means the approval gate is friction without value and a healthy 15 to 30 percent means it… 1 Approval gate Optional workflow step requiring human sign-off before remediation executes. 2× Approval SLA The maximum time window, often 24 hours, within which an approval-gated remediation must be responded to, after which the action auto-cancels rather than executing without approval. 1 Architect-design lever The fourth and highest-ceiling optimization lever, changing the workload's architecture to cost less (for example replacing a 24/7 service with a serverless equivalent), applied… 1 Architectural boundary A limit enforced by design rather than configuration, as with ZopNight's read-only MCP layer where writes are simply not implemented so there is no toggle to flip or scope to grant. 1 Architectural ceiling The structural cost base of a workload that remains after operational optimizations such as scheduling, rightsizing, and rate optimization are exhausted, and which stays with… 1 Architectural differentiation A competitive edge that comes from structural design choices rather than feature lists, such as being MCP-native, read-only by design, and built on an open protocol. 1 Archive tier Audit retention; right-size per tier; configure lifecycle policies. Move old backups to archive tier. Quarterly review. 1 Assertion Consumer Service The SAML endpoint URL on ZopNight's side (for example https://app.zopnight.com/auth/saml/<domain>/callback) where the identity provider posts the signed SAML assertion after the… 1 Assume-role ZopNight connects to AWS via an IAM role with cross-account assume-role trust. The role grants the minimum permissions needed for each capability. The customer can grant or deny… 2× Asymmetric risk A situation where the downside cost far exceeds the upside benefit, as with database writes where a failed change can cost six figures in downtime and trust, justifying the… 1 Attribute mapping The configuration of which identity-provider user attributes map to ZopNight fields, requiring at least email, recommending name, and enabling automatic team assignment when… 1 Audience mismatch A SAML validation failure caused by metadata drift where the Audience URI in the assertion does not match the Entity ID configured in ZopNight, fixed by making the two values… 1 Audience translation Converting engineering terminology into language a non-technical audience understands, such as rendering technical detail as business terms like access control or cost flow when… 1 Audit log Per-org record of all mutating API calls. 2× Audit log vs notifications The distinction that the audit log is the immutable source of truth recording every event regardless of notification settings, while notifications are only a delivery mechanism… 1 Audit-log integrity The guarantee that audit entries are append-only and tamper-resistant, enforced by an INSERT-only MySQL table with no UPDATE permission and per-entry hashes chained to the… 1 Authority bounds Authority bounds vary by severity. The matrix should be explicit about what's permitted at each level: 1 Authorization code flow The OAuth 2.0 flow where the user is redirected to the identity provider, authenticates and authorizes access, and is redirected back with a single-use authorization code that… 1 Auto-escalation Persistent anomalies become emergencies. The auto-escalation is the safety net. 2× Auto-expiry The auto-expiry is critical. Manual cleanup gets forgotten and freezes drift. 1 Auto-promote Auto-promote makes the transition explicit. The user clearly chose to take ownership. 2× Auto-remediation trigger A state-history trigger type indicating a recommendation rule fired and executed auto-remediation, shown in a format like auto-rem:RC-001 (Idle EC2) that links through to the… 1 Auto-remediation workflow The ordered three or four step process (Precondition, optional Approval, Action, and Validate) that runs each auto-remediation, where every step has a defined success or failure… 1 Auto-sequencing Auto-sequencing covers 80% of cases. Most groups need no custom configuration. 1 Auto-tag Cloud-native tag vs ZopNight auto-tag attribution: 1 Auto-tagger The auto-tagger makes two kinds of predictions per resource: 2× Autopilot mode The autoscaling mode in which the autoscaler manages capacity automatically without per-action approval, adopted per policy as teams progress from monitor to recommend to… 1 Autoterm vs schedule In Databricks SQL Warehouse cost control, the choice between autoterm (auto-pause after a few minutes of inactivity, suited to always-available workloads) and an explicit schedule… 1 Avoidable spend Spend on resources flagged as idle / orphan / over-provisioned. 2× AWS Organizations Concepts: - AWS Organizations: the top-level container that owns multiple AWS accounts. - OU (Organizational Unit): a folder-like grouping of accounts. Service Control Policies… 2× Azure Hybrid Benefit Layer 5: Azure Hybrid Benefit. A customer with on-prem Windows or SQL Server licenses can bring them to Azure and avoid paying for the license portion of the VM cost. Typical… 2× Azure Management Group Azure's hierarchical grouping of subscriptions with inheritable policies, analogous to AWS Organizations or GCP Folders, sitting above the subscription which is the billing and… 1 Azure reservation A reservation utilization report shows 62% utilization on a 3-year Azure Reservation. The defensible action: 2×
Reference / Glossary
Every term,
in one place.
838 terms across 237 lessons, each with a definition pulled verbatim from the lesson that first uses it. Click any term to land there.
Backup retention The length of time backups are kept, a direct driver of monthly storage cost, disciplined so that retention matches RTO, RPO, and compliance requirements and no more rather than… 1 Batch API Bedrock offers batch API at ~50% of on-demand pricing. Workloads with relaxed latency requirements should use it. 1 Bearer credential PAT management is covered in detail in M6.3. For now: read-only is the only scope option (architectural; see M6.1.L2 and M6.6); the token is bearer credential (treat like a password). 2× Bedrock pricing AWS Bedrock's token-based pricing that charges per input token plus per output token at rates varying widely by model (for example Opus at $15 and $75 per million tokens versus… 1 Bedrock rule One of the ten ML and Bedrock recommendation rules (RC-1601 through RC-1610) that each target a specific cost pattern such as model selection optimization, provisioned throughput… 1 Belt-and-suspenders cron A redundant stop cron added to a schedule (such as a weekend midnight stop on a weekday-only schedule) that is harmless during normal operation but catches the edge case of a… 1 BigQuery billing export GCP BigQuery billing export. GCP doesn't have a CUR-equivalent file drop. Instead, billing data exports directly to a BigQuery dataset. One row per SKU per resource per day.… 1 BigQuery slots GCP BigQuery's reserved query capacity purchased as a flat-rate commitment for predictable workloads, offering an alternative to on-demand per-terabyte pricing where a single… 1 BilledCost - The set of columns (about 50 in FOCUS 1.0: BilledCost, EffectiveCost, ServiceName, ResourceId, RegionId, RegionName, ChargePeriodStart, etc.) - The data types and allowed values… 1 Blameless culture A blameless culture is essential. Postmortems focus on systems and processes, not individual actions. "Bob ran the cleanup script wrong" is bad; "the cleanup script didn't surface… 1 Blameless postmortem Incident comm template + practiced cadence. Per-audience messaging. Blameless postmortem. 1 Blast radius The math: a single-account org has a blast radius equal to its entire estate. An org split across 15 accounts has at most 1/15 the average blast radius per incident, and in… 2× Body capture By default, the full request body and response body are stored. This is "body capture mode"; the audit log answers not just "what endpoint was hit" but "with what data, returning… 2× Bookmark The default is the org's primary landing; each user's bookmark is their personal landing. The two can differ. The default matters most for new joiners and casual visitors. 1 Bottom-up forecast Draft a bottom-up forecast for your team: 1 Breadcrumb When viewing children, a breadcrumb shows the path: 2× Break-glass path This is the break-glass path. Use rarely; document thoroughly. 1 Break-glass procedure Even ZopNight engineers cannot read a customer's credential. The vault decryption key is not accessible from engineering tooling. Production debugging that needs credential access… 1 Breakeven calculation A reliability investment analysis that invests only when downtime hours avoided times cost per hour exceeds the annual reliability cost, for example Multi-AZ RDS at $4,800 per… 1 Budget Spend limit per resource/group/team with threshold notifications. 1 Budget conversation Establish (or audit) your monthly + quarterly budget conversation cadence. Document the agenda template; share with attendees ahead of meetings. Use ZopNight's Budget Health… 1 Budget pyramid The budget pyramid is a layered budget structure where each level rolls up to the level above. Org budget is the apex; business unit (BU) budgets sit beneath; team budgets sit… 1 Bulk accept Bulk accept on high-confidence predictions is the fastest path to coverage. 1 Bulk action Multi-resource start/stop or attach operation via 4-worker pool. 1 Bulk membership Adding or removing many resources from a resource group in one operation by reusing the filter machinery to construct a filter, multi-select the matches, and add hundreds of… 1 Business Hours preset The Business Hours preset has three crons. The third is a redundant weekend stop. The reason it exists: 1 By Resource layout One of the five Cost Flow Sankey layouts, cascading Account to Service to Resource to Team, used for deep diagnosis and anomaly investigation to find which specific resources… 1 By Service layout One of the five Cost Flow Sankey layouts, cascading Provider to Account to Service to Team, used to identify which cloud services dominate spend, for example whether cost is… 1 Byte-accurate restore The byte-accurate restore is the safety net. Replace becomes safe because Remove always works. 1 Byte-accurate rollback The byte-accurate rollback is what makes Event Readiness safe. 1
Cadence Inform fails when one report tries to serve three audiences. Engineering, finance, and leadership each need a different cadence, granularity, and shape. 1 CAGR Compound Annual Growth Rate, used as a calibration check on the growth-rate input to top-down forecasting, where a historical CAGR anchors and validates a synthesized forward… 1 Calibration loop The quarterly iterative process of measuring historical forecast variance, identifying systematic bias, applying a correction factor to future forecasts, and verifying the result,… 1 Cancel override Terminate an active override before its scheduled expiry to resume normal resource operation when the situation it addressed resolves early. 1 Canonical tag set The minimal starting set of mandatory and recommended organizational tags, typically environment, team, owner, and cost-center, enforced and maintained as code to reduce tag debt. 1 Carbon Aware SDK For implementation: the Carbon Aware SDK provides a runtime signal "is the grid clean right now?" that orchestrators can use to decide whether to run workloads. 1 Carbon intensity Cloud workloads consume electricity. The electricity has a carbon intensity that varies by region (the grid mix: coal, gas, hydro, solar, wind, nuclear). The same workload in… 1 Carbon intensity metric The measurement of carbon emissions in grams of CO2 per kilowatt-hour from electricity generation, which varies by grid region and time of day. 1 Carbon reporting cadence The frequency and structure for reporting cloud carbon footprint to leadership, typically quarterly or annually, following trend, breakdown, intensity, and comparison. 1 Carbon-aware computing Carbon-aware computing is the practice of scheduling compute to align with low-carbon energy availability. The grid's carbon intensity varies throughout the day (solar peaks at… 1 Carbon-aware scheduling Scheduling compute workloads to align with low-carbon energy availability on the grid, since carbon intensity varies throughout the day. 1 Cascade 3 layout switches in 90 seconds. Each switch reframed the cascade to surface the next-level question. 1 Cascade investigation Investigating cost anomalies by drilling from the broadest dimension down through progressively narrower ones, org to cloud account to team to resource group to resource, to… 1 Cascading savings Cascading savings are a feature, not a bug. The rule's projection focuses on its scope; real cleanup recovers more. 1 Catastrophic protection A reliability investment justified by the potential cost of trust damage and organizational impact that a failure on a critical business system would cause. 1 Cause probability The probabilistic ranking of potential root causes for a cost anomaly, expressed as a percentage indicating how likely each cause explains the observed deviation. 1 CDCR Continuous Detect, Continuous Remediation. The operating model. 1 CDCR boundaries The four explicit limits of Continuous Detect, Continuous Remediation: it is not autopilot for everything, not a bypass for change management, not a substitute for cost ownership,… 1 Centralized monitoring A shared-services architecture where monitoring, logging, and observability run in a dedicated platform-team account rather than being duplicated across team-owned accounts. 1 Certified rule Shorthand for a recommendation rule on the auto-remediation allowlist (validated end-to-end on real cloud). About 124 rules are allowlisted (roughly 28 one-click auto plus 96… 1 Change management integration Wiring CDCR approval-gated remediation into existing change-management processes to preserve audit trails, cross-team awareness, and rollback playbooks. 1 Chaos engineering Deliberately introducing failures such as killing components into production or test environments to verify reliability assumptions. 1 Chargeback These are not synonyms. Showback and chargeback differ in whether money actually moves. Allocation is the math underneath either of them. 2× Chargeback anti-pattern The condition where chargeback complexity grows until maintaining it costs more than the savings or accountability it enables, warranting simplification or rollback to showback. 1 Claude Code Claude Code is Anthropic's CLI agent. It runs in a terminal, reads/writes local files, executes shell commands (with permission), and calls MCP servers. It is the right surface… 1 Client ID / Secret The credential pair an OAuth provider such as Google, GitHub, or Azure issues to authenticate an application and authorize users on its behalf. 1 Clone Presets are immutable templates. To make a dashboard specific to your team, clone the preset first (this creates a new saved dashboard), then modify the clone. The original preset… 1 Cloud Asset Inventory Cloud Asset Inventory is GCP's equivalent of RE2. ZopNight calls Asset Inventory with ContentType_RESOURCE to enumerate the estate: 1 CloudFormation StackSet - The role is deployed via CloudFormation StackSet to every member account - Each role has the same name and same external ID per ZopNight organization - ZopNight discovers all… 1 Cluster scheduling layer ZopNight's daily lifecycle management of start and stop times for Databricks clusters, working alongside Databricks native autotermination to cut compute cost. 1 COALESCE pattern The COALESCE pattern gives the best-available-answer per day: actual where available, calculated where not. The week label is actual (because some days were actual) but the… 1 Codex MCP A Model Context Protocol integration that lets OpenAI's Codex tool read ZopNight cost data inline during development. 1 Cold-start latency Cold-start latency of 3 minutes per test run: 2× Combined business case A scheduling justification that weighs both cost savings and carbon impact as complementary reasons to manage a resource. 1 Commander authority The decision-making power granted to a single incident commander during a cost SEV-1 or SEV-2 to coordinate response, approve actions, and communicate outcomes. 1 Commitment portfolio The major clouds offer four commitment-style instruments that trade flexibility for discount. Knowing which fits which workload is the foundation of commitment portfolio strategy. 1 Commitment utilization The percentage of purchased Reserved Instances, Savings Plans, or Committed Use Discounts actually consumed during their term, tracked as an Operate KPI. 1 Committed Use Discount Committed Use Discount (CUD). GCP's equivalent of AWS Reserved Instances or Azure Reservations, but with two flavors. Resource-based CUD commits to a specific machine family in a… 2× Communication templates Standardized message formats for different audiences such as engineering, finance, leadership, and security during a cost incident to keep detail appropriate per stakeholder. 1 Complexity drift The accumulation of allocation rules and special cases in a chargeback system until the effort to maintain it exceeds its cost-savings or accountability value. 1 Composite budget A mid-size org's composite budget structure: 1 Composite scoring The composite scoring is robust to confused naming. 1 Compound optimization The compound optimization (cheaper model + batch) captures 90% of cost. 1 Compounding savings Cost reductions that persist quarter over quarter and build on prior gains, enabled by a consistent weekly Operate cadence and governance. 1 Compromise response The immediate actions taken when credentials are leaked: revoke the credential, rotate replacements via a secret manager, audit affected resources, and contain the blast radius. 1 Compromise-driven cost incident A cost spike caused by compromised cloud credentials that launch unauthorized workloads, classified as SEV-1 because of its security implications. 1 Concurrent event constraint A limit on how many event-readiness scaling actions can run simultaneously across cloud targets to avoid overloading infrastructure during coordinated events. 1 Confidence band Event Readiness shows a cost estimate before commit. The estimate has a confidence band, an isEstimated flag, and a breakdown by target. 5× Confidence band communication Presenting forecasts to non-engineering audiences as a range rather than a single point to reflect the underlying uncertainty. 1 Confidence score Each prediction has a confidence score. Customers accept or reject. 1 Confirmation fatigue The degradation of approval workflows where frequent prompts get rubber-stamped, turning thoughtful review into automatic acceptance. 2× Confirmation modal The confirmation modal is intentional friction. A misclick on Stop should not silently terminate a running prod resource. The modal is brief but explicit. 1 Confused deputy The external ID is mandatory. It is generated unique per customer organization in ZopNight and prevents the confused deputy attack (where one customer's account ID could be used… 2× Connection-pool math The calculation of whether available database connections will exhaust under load, the primary diagnostic for database bottlenecks during traffic spikes rather than CPU saturation. 1 Control mapping Pre-built compliance reports live at Settings → Compliance Reports: one-click generation for SOC 2, ISO 27001, quarterly RBAC review, and others. For framework-specific needs,… 1 Conversation breakdown If conversation breakdown signals are present, plan an off-site or facilitated session to reset. The cost of a broken conversation is higher than the cost of fixing it. 1 Cooldown A scaling policy with no cooldown sees rapid scale-up + scale-down oscillation. The fix: 1 Cost allocation method A strategy for distributing shared infrastructure cost back to consuming teams based on usage, headcount, or another proportional metric. 1 Cost approval threshold A spend limit configured in CI/CD that requires extra review or sign-off when an infrastructure change would exceed it, preventing ungated cost growth. 1 Cost Breakdown card The Cost Breakdown card is the most integrated view, switching toggles within one card. For dedicated analysis, the separate Trend and Flow reports give more space and richer drill. 1 Cost commander handoff The transition of the cost-incident commander role from one person to another to prevent decision fatigue during a long incident. 1 Cost estimate Event Readiness shows a cost estimate before commit. The estimate has a confidence band, an isEstimated flag, and a breakdown by target. 1 Cost Explorer AWS Cost Explorer. A query interface on top of an internally aggregated CUR. Live in the AWS console. Up to 14-month history. Easy to filter and group. The data is mostly the same… 1 Cost Flow Switch between Trend and Flow in Reports → Cost Breakdown or in dedicated Trend (Reports → Cost Trend) and Flow (Reports → Cost Flow) views. Filters transfer between the two; time… 1 Cost isolation A reporting view that keeps per-account or per-resource costs distinct and visible rather than aggregated into one number. 1 Cost of detect-only The annualized cost of detect-only is the business case for CDCR investment. 1 Cost of downtime The financial impact per unit of time, usually per hour, when a service is unavailable, combining lost revenue and other business impact. 1 Cost ownership Cost ownership lives with the team that uses the resource. Not with central FinOps. Not with finance. Not with the platform team. Central groups enable; the consuming team owns.… 1 Cost rollup The aggregation of costs across multiple accounts or resources into a single total, typically for org-wide financial reporting. 1 Cost runaway A sudden, unexplained increase in cloud spend that signals a potential incident requiring immediate investigation and possible remediation. 1 Cost SEV Cost SEV criteria + response playbook in team runbook. Test annually with a drill. 1 Cost shape The pattern or trajectory of cost over time for a workload or initiative, used in forecasting and capacity planning. 1 Cost source label A report indicator showing whether the underlying cost data is post-discount billing from cloud APIs or calculated rack rate. 1 Cost Trend Switch between Trend and Flow in Reports → Cost Breakdown or in dedicated Trend (Reports → Cost Trend) and Flow (Reports → Cost Flow) views. Filters transfer between the two; time… 1 cost_allocation_daily Internally, ZopNight computes daily allocations into a single cost_allocation_daily table with a dimension_type column. Reports query this table with filters. The three dimensions… 1 cost_source cost_source is per-row in cost_records. Rollup tables (daily / monthly aggregates) derive their own cost_source: 1 Cost-per-X Unit economics is the practice of dividing cost by a business denominator to get a cost-per-X number. Denominators include Monthly Active Users (MAU), orders, requests, tenants,… 2× Cost-recovery vs quality category The distinction between rules that directly cut spend, cost-recovery, and rules addressing governance, security, or reliability debt, quality, which pay back through avoided incidents. 1 Coverage - Coverage at category level (Compute, Kubernetes, Database, Storage, etc.) - Granted / Denied / Unknown badge per resource type per region - Exact error message for any Denied… 2× Coverage trend The tracking of tag-coverage percentages over weeks or quarters to show whether tagging discipline is improving or declining. 1 Crawl stage The first maturity level, where the organization has cost visibility through dashboards and reports but lacks team-level cost ownership and action. 1 Crawl-Walk-Run A three-stage FinOps maturity model where Crawl is visibility only, Walk is optimization that decays, and Run is sustained operational cadence. 1 Credential rotation The periodic renewal or replacement of long-lived cloud access credentials, favoring modern patterns such as assume-role and Workload Identity Federation. 1 Critical severity A finding level indicating security risk or major cost waste that requires same-day response. 1 Cron expression Schedule firing pattern. 5-field format. 2× CronJob suspend The Kubernetes action of pausing a CronJob's schedule to prevent workload runs during specific windows. 1 Cronstrue The preview is generated by the cronstrue library (the industry standard for cron-to-prose conversion). If you have any doubt about a cron's behavior, trust the preview. 1 Cross-account credential Configure each cloud account independently in Settings → Cloud Accounts. The setup wizard guides through the cross-account credential pattern for each cloud (covered in L3 in detail). 1 Cross-account dependency A relationship where a workload in one cloud account relies on a service in another, requiring coordinated scheduling. 1 Cross-account group Cross-account group with one schedule attached: 1 Cross-AZ traffic The 8% network line is the cross-zone chatter cost. It is not a GCP-only surprise: AWS bills the same cross-AZ traffic at $0.01 per GB each direction, so this workload would cost… 2× Cross-cluster group A resource group spanning multiple Kubernetes clusters so one schedule applies across cluster boundaries without per-cluster duplication. 1 Cross-region egress Network traffic leaving one cloud region for another, incurring per-GB charges that compound significantly at scale. 1 Cross-stage anti-pattern A structural FinOps problem that can appear at any maturity stage and tends to worsen as the organization advances. 1 Cross-team role An RBAC role with allResources set true that grants access across the entire organization rather than to a single team's resources. 1 CSV upload If your endpoint is internal-only (private IP / VPN-only), Pull API will not work. Switch to Push API or CSV upload. 1 CUD GCP Committed Use Discount. 1 CUR AWS Cost and Usage Report (CUR). The raw fact table. One row per resource per usage type per day (or hour, if configured). Lands as gzipped CSV or Parquet in an S3 bucket. Daily… 1 Currency reconciliation Converting cloud bills from multiple currencies into one reporting currency using date-specific exchange rates so totals match the invoices. 1 Cursor command A reusable AI-agent instruction file saved in the .cursor/commands/ format that teams invoke by name to run a consistent workflow. 1 Cursor MCP Connecting ZopNight's MCP server to the Cursor editor so an agent can query cost, recommendation, and audit data, with the PAT supplied through an environment variable reference… 1 Cursor pagination The Audit Log page at Settings → Audit Log supports all filters and exports. For programmatic access, the Audit API handles the same filter vocabulary with cursor pagination. 1 Custom role The system-role design is a deliberate trade. You sacrifice some granularity (a FinOps Analyst who wants to dismiss but not apply recommendations needs a custom role) in exchange… 2× Custom sequence The custom sequence runs strictly in order. Each step waits for the previous to complete (with timeout) before proceeding. 1 Customer-execution rule A recommendation, such as the Bedrock rules, that ZopNight can only surface and quantify because the actual fix requires customer-side code or config changes; ZopNight stays… 1 Customization The clone pattern decouples customer customization from preset evolution: 1
Daily billing 24-hour lagged actual cost from cloud APIs. 1 Data residency A regulatory or compliance requirement that data for certain customers stay in a specific region or cloud, which is a common reason orgs run a tactical second cloud or split accounts. 1 Database denylist Hardcoded set of resource types ZopNight refuses to auto-mutate. 2× Databricks autoterm Databricks autoterm vs ZopNight scheduling: 1 Databricks Cluster A Spark compute cluster inside a Databricks Workspace that runs jobs and interactive notebooks, discovered by ZopNight as a schedulable target and usually the main Databricks cost… 1 Databricks Job A Databricks scheduler that runs work on a cluster; ZopNight does not discover jobs as billable entities because the cost lives in the cluster the job runs on, though jobs… 1 Databricks Workspace The top-level Databricks tenant, per region with its own URL and authentication, that contains Clusters, Instance Pools, and SQL Warehouses as schedulable child resources. 1 Date-specific exchange rate The FX rate as of the specific date of a charge, used to convert a non-USD cloud bill to USD, because there is no single exchange rate and using today's rate for a past charge… 1 Day 90 review The 45-minute assessment at the end of a 90-day maturity move-up plan that checks whether the plan's specific, measurable goals were met, and which doubles as the kickoff for the… 1 Day-of-week field The cron field (0-6, Sunday = 0) that sets which weekdays a schedule fires; 1-5 means Monday through Friday and 0,6 means the weekend, and it must not be confused with the… 1 DB event readiness The monitor-only mode for databases during a traffic event, where ZopNight surfaces recommendations (raise connection limits, add read replicas, pre-warm caches) for a DBA to… 1 Deallocate Azure VM state where compute billing stops (different from "Stop"). 1 Decision matrix The "right path" depends on context. The decision matrix gives the starting point. 1 Decision tree The exception applies when steps 1–3 of the decision tree have already been done. Before any of those steps, the default for non-prod is "schedule, do not commit." 1 Decomposition The decomposition is what makes the response proportionate. Raising the entire $30K would normalize waste; enforcing on the entire $30K would punish legitimate growth. 1 Deep-link This is the bridge between "Cost Flow analysis" (where the money goes) and "Recommendations action" (what to do about it). Without the deep-link, the user would have to read the… 1 Default dashboard Every ZopNight org has exactly one default dashboard. This is the dashboard new users land on when they first sign in, and the one any user sees on /dashboard if they haven't… 1 Default-deny The policy model is default-deny. If a new endpoint is added without a policy mapping, the gateway rejects all requests to it. This catches accidental over-exposure during… 1 Defense in depth Layering multiple independent controls so no single failure grants unauthorized access, for example gateway-level RBAC enforcement that blocks a request before the backend sees… 1 Degraded status A connection or discovery status indicating a cloud account or discovery process is partially failing rather than fully working, typically routed as a WARNING-severity notification. 1 Demo-env audit ZopNight schedule per demo environment. Annual demo-env audit. Decommission obsolete; schedule active; pre-warm per-demo when applicable. 1 Demo-prod environment A production-like environment kept for sales demos, customer showcases, training, and investor pitches, scheduled for business hours plus on-demand start because its audience is… 1 Denominator Unit economics is the practice of dividing cost by a business denominator to get a cost-per-X number. Denominators include Monthly Active Users (MAU), orders, requests, tenants,… 2× Dependency warning The alert ZopNight raises at schedule-attachment time when a resource, such as a Databricks cluster, has dependent jobs scheduled to run during the selected off-hours, so the… 1 Detach Detaching does NOT change the resource's current state. If the resource was running at the time of detach, it stays running. The schedule simply no longer manages it. 1 Diffusion of responsibility The single biggest benefit of an explicit matrix is avoiding diffusion of responsibility: 1 dimension_source The dimension_source field on a tag indicates: 2× Dimensional cascade Investigating a cost anomaly by moving from the broadest dimension to the narrowest (org-level, cloud-account, resource-group, resource) to find the specific resource driving the spike. 1 Dimensional redundancy The pattern where a cost shift between teams nets to no org-level change, so ZopNight suppresses the offsetting team-level anomalies as noise while still firing org-level and… 1 Direct attribution If category 1 is below 70% of total cost, focus on tag discipline before chargeback. Direct attribution is the simplest case; everything else compounds complexity. 1 Discount stack Billing cost can be 10 to 60 percent below rack rate depending on the discount stack. Eight layers stack on top of the rate card, in approximately this order of application: 1 Dispute resolution Chargeback systems often start simple and become Byzantine. The fix is upfront design that handles edge cases: naming the categories of cost, documenting allocation rules in… 1 Domain allowlist The trade-off: OAuth has no built-in domain restriction. Any Google account can attempt sign-in. For most orgs, that's not acceptable as-is. ZopNight applies a domain allowlist… 2× Double-lever scheduling The property that scheduling cuts compute hours, which reduces both cost and carbon emissions at the same time; the two savings percentages differ, though, because grid carbon… 1 Drafting vs executing The distinction between using an AI agent to draft artifacts like memos, tickets, and incident comms (where agents win) versus taking action, which the read-only agent does not do. 1 Drift Cloud-side state change ZopNight detects but didn't initiate. 1 Drift detection For drift detection, ZopNight monitors week-over-week coverage and surfaces alerts when coverage drops more than 2 percentage points in a week. The alert links directly to the… 1 Drift detection cadence The 6-hour discovery cron cadence at which ZopNight catches tag drift within the day, paired with a weekly review to keep drift from accumulating and hold tag coverage at 95%+. 1 Drift rate A team with a consistent 5%+ drift rate week over week: 1 Drift resolution Reconciling detected tag drift between the cloud's tags and ZopNight's expected values via one of three paths: trust cloud, trust ZopNight, or re-evaluate. 1 Drift response pattern The appropriate remediation for an IaC drift event once it is classified by source, whether intentional, accidental, or unauthorized manual changes that diverge from Terraform,… 1 Drift trigger A state-history trigger value (drift: cloud-side) indicating the cloud resource's state changed outside ZopNight, distinguishing it from schedule, manual, override, and… 1 Drill-down Navigating from a broad cost view into a specific resource, for example clicking a Sankey node in Cost Flow and using the breadcrumb to answer a question in under 60 seconds. 1 Driver analysis Explaining what factors would push a forecast higher or lower (feature launches, growth-rate variance, one-time projects) so a forecast band is communicated honestly rather than… 1 Driver-based forecasting Driver-based forecasting (vs extrapolation): 1 DST handling ZopNight interpreting crons in the schedule's IANA timezone so a cron fires at the same local clock time year-round, automatically absorbing daylight saving transitions without… 1
EC2-Other The "EC2-Other" line item on AWS bills typically includes: 1 editable=false For policies in the three refusal categories, the UI marks them editable=false: 1 Editor ZopNight ships with four system roles: Viewer, Editor, Admin, and SuperAdmin (default_roles.go), designed to cover the common 80% of role assignments without custom-role work.… 1 Effective discount Realized discount: rate-card × coverage × utilization. 5× EffectiveCost - The set of columns (about 50 in FOCUS 1.0: BilledCost, EffectiveCost, ServiceName, ResourceId, RegionId, RegionName, ChargePeriodStart, etc.) - The data types and allowed values… 1 Egress Cloud network traffic leaving the cloud or crossing zones. 1 Elastic IP AWS charges $0.005 per hour ($3.60 per month) for any Elastic IP that is not attached to a running instance. The fee exists to discourage IP hoarding. Detection: EIPs in… 1 Eliminate waste The first and fastest optimization lever: stop paying for things nobody uses, such as scheduling non-prod off-hours, terminating idle resources, releasing orphan storage, and… 1 Enforce For each budget overrun, investigate and decompose. Document the raise + enforce decisions in the budget's notes. ZopNight's audit log captures the budget adjustment with reason… 1 Engineering preset A ZopNight dashboard preset for day-to-day platform team use, featuring resource health, schedule execution status, recommendations to triage, and anomaly detection. 1 Enterprise Discount Program Layer 6: Enterprise Discount Program (EDP). A negotiated additional discount, typically a single percentage off everything, in exchange for a multi-year minimum spend commitment.… 1 Entity ID The SAML config is stored in the customer's tenant database, encrypted at rest. The certificate is stored separately in the secret manager. Validation happens at the gateway: when… 1 Env-var loading Supplying secrets like a ZopNight PAT to MCP clients through shell environment variables referenced in config (for example ${env:VAR}) rather than committing literal values, so… 1 Environment prediction The auto-tagger's inference of a resource's environment (dev, test, stage, prod) with a confidence score, which the customer accepts or rejects, one of the two core auto-tag… 1 Environment schedule A schedule pattern defined per environment type (dev, test, stage, prod), based on when each environment is actually used, then rolled out, monitored, and refined. 1 Ephemeral demo environment A demo environment provisioned per demo and torn down after use, distinct from a persistent demo-prod environment that runs on a business-hours plus on-demand schedule. 1 Equal split When a resource has a single team owner, attribution is trivial. The tag tells you who. The hard cases are shared resources: load balancers, databases, Kubernetes clusters,… 1 Error class triage Classifying a failed auto-remediation into one of three classes, user_action (customer self-fixes, e.g. missing IAM permission), transient (wait and retry), or system (escalate),… 1 Escalation chain Each budget can have multiple thresholds: percentage levels of the budget that trigger a notification when spend crosses them. Thresholds combined into an escalation chain drive a… 2× Escalation matrix An escalation matrix is a documented mapping of anomaly severity → who responds, when, and with what authority. Without it, on-calls default to "I'll handle it" or "someone else… 1 ESG narrative A carbon report framed for leadership and investors that turns the cloud carbon footprint into a tracked KPI, adapted per audience (CEO, sustainability team, investors) rather… 1 ESG reporting For ESG reporting, ensure methodology is documented and auditable. ZopNight's roadmap includes ESG report exports. 1 Evaluate Evaluate is where the rule's logic lives. Given a resource and its state history, it returns: - *Recommendation: the rule fired (finding generated) - nil: no finding (resource is… 1 Event lifecycle Event lifecycle has clear states with defined transitions: 1 Event log Every autoscaler policy maintains an event log of all lifecycle events and scaling actions. The event log is the diagnostic surface. When scaling behaves unexpectedly, the event… 1 Event log retention The per-policy event log an autoscaler maintains of all lifecycle and scaling actions, which serves as the diagnostic surface for explaining why scaling behaved a certain way. 1 Event Readiness Pre-scale infrastructure for known traffic events. 1 Evidence panel The composite score balances multiple signals; the evidence panel exposes the math. 2× Exclusive membership A resource can be attached to at most one schedule at a time. This is the exclusive membership rule. 2× Executive preset A ZopNight dashboard preset for leadership and finance, showing high-level cost trend, top costly resources, budget health versus forecast, and savings over time, with no… 1 Exit clause A contract term governing how an org can leave a share-of-savings commitment vendor arrangement, evaluated when deciding whether such a vendor fits. 1 Expected event A cost anomaly with a known, documented cause such as a marketing campaign or planned launch, which the severity-times-expectedness matrix treats as an event rather than an… 1 Expected requests model The load test is what makes Expected Requests model accurate. 1 Expired override An override that has passed its expiry time and no longer suspends the schedule, shown on the Overrides page with a relative-time display such as "expired 30m ago." 1 Expiry Overrides are for time-bounded exceptions. They suspend or force a resource's state for a defined window with an explicit expiry. After the expiry, the schedule resumes normal… 1 ExpressRoute Azure's dedicated private network connection between on-premises and Azure that bypasses the public internet, with its own pricing model. Inter-zone bandwidth within a region is… 1 External ID The external ID is mandatory. It is generated unique per customer organization in ZopNight and prevents the confused deputy attack (where one customer's account ID could be used… 1 ExternalId For AWS, the ExternalId field on the IAM role trust policy is critical. It defends against the confused deputy attack, where an attacker tricks ZopNight into assuming a role they… 1
False positive guards Design choices that reduce false alarms, such as requiring multiple signals before flagging a resource as abandoned, or using soft budget alerts instead of hard enforcement… 1 False precision Some leaders push for false precision: "Just give me the number." The graceful response: 1 Filter dimension One of the audit log's queryable fields (user, path, status, date, and similar) that lets an investigator narrow thousands of entries to the few directly relevant to a forensic or… 1 FinOps Foundation Cross-vendor industry body publishing the canonical framework. 2× FinOps lifecycle The FinOps Foundation's three iterative phases of cloud financial management: Inform, Optimize, and Operate. 1 FinOps preset A ZopNight dashboard preset for the dedicated FinOps practitioner, featuring the cost flow Sankey, team-level showback, budget versus spend per team, tag coverage trend, anomaly… 1 Floor commit The commitment strategy of buying reservations or savings plans to cover only the predictable steady-state floor of usage, while covering peaks with on-demand or spot capacity. 1 FOCUS FinOps Open Cost and Usage Specification. Open standard for cost data. 1 Force-off - Force-on (override_type=1): the resource (or group) stays ON during the window. Schedule stop crons are ignored. - Force-off (override_type=0): the resource (or group) stays OFF… 1 Force-on - Force-on (override_type=1): the resource (or group) stays ON during the window. Schedule stop crons are ignored. - Force-off (override_type=0): the resource (or group) stays OFF… 1 Force-on / force-off Override types that suspend schedule firing in one direction. 1 Force-on override An override (override_type=1) that keeps a resource or group ON during a window, causing the schedule's stop crons to be ignored; its counterpart is force-off. 1 Forecast Conflating them produces dysfunction: people argue about budget when they should be discussing forecast; alerts get treated as enforcement when they are notifications; forecasts… 2× Forecast accuracy For variance analysis, the report compares "forecast at time T" vs "actual at time T+N" for past periods, surfacing forecast accuracy trends. 2× Forecast log Run hybrid forecasting quarterly. Document each reconciliation in the forecast log. ZopNight's Forecast report supports the side-by-side comparison and the committed forecast tracking. 1 Forecast template A structured per-team form used in bottom-up forecasting, where each team forecasts resource by resource, accounts for planned events, and submits to FinOps for aggregation. 1 Forensic query An audit log query, enabled by full request and response body capture, that answers a specific investigation question with complete detail rather than just noting that an action… 1 Forgotten account A low-usage cloud account with no clear owner, often created for a past experiment, that is a candidate for consolidation into a parent account. 1 Forgotten resource A long-running resource nobody remembers, the single most common cause of cost anomalies (around 25%), showing up as gradual cost drift over weeks with no new resources. 1 Four-layer compliance Org-level MCP toggle is the foundation. Default disabled; opt-in deliberately. Document the four-layer compliance posture for CISO conversations. 1 Freeze window Freeze window: a defined period when normal schedules don't fire. Resources stay in their current state (typically running) regardless of what their schedule would normally do.… 1 Frontend gate If a frontend gate were to disagree with the gateway (e.g., frontend cached an old policy set), the worst case is a 403 from the gateway and a corresponding "Access restricted"… 1 Full response logging An optional audit setting that captures full MCP response bodies for compliance; it is off by default because it increases audit log volume 10-50x and puts sensitive cost data… 1 Functional tagging Reorg-proof tagging that labels a resource by what it does or which business function it serves rather than by the team that currently owns it, so tags survive org-chart changes. 1 FX rate A team builds a report that re-converts cost values to USD every time the report is rendered, using the live FX rate. Most likely problem: 1
Gap (schedule) An uncovered time window in a schedule, spotted on the 24-hour weekly grid before saving, that would otherwise leave resources running or stopped against the intended coverage. 1 Gateway The v3 consolidation merged the table to a small set of stable, user-facing core entities. The mapping from entity to backend services is internal and managed by the gateway. From… 1 Gating criteria ZopNight's gating criteria for adding write tools: 1 GCP Folder A grouping node in the GCP resource hierarchy (Organization to Folder to Project) that holds projects and enables policy inheritance, the GCP counterpart to an AWS Organizational… 1 Global search - Default Parents view with child-count badges per parent - Click child badge → Children view with breadcrumb navigation - Per-scope filters that adapt to the current view -… 1 gp3 A bill row is not the same as a "resource." A single EC2 instance generates compute rows (EC2-Instance), storage rows (EBS:VolumeUsage.gp3, EBS:SnapshotUsage), network rows… 1 GPU scheduling Pausing GPU instances during off-hours when training jobs are intermittent rather than running them 24/7, typically capturing 60 to 90 percent of cost savings for ML training workloads. 1 Graduated authority CDCR's act layer is not a single big red button. It is a graduated authority model: 1 Granted / Denied / Unknown Permission Visibility states. 1 Graviton Graviton (ARM) vs traditional x86 instances: 1 Grid intensity API A real-time or forecast API (such as electricitymaps.com or WattTime) that reports the carbon intensity of a region's electrical grid, enabling carbon-aware scheduling of flexible… 1 Grid mix Cloud workloads consume electricity. The electricity has a carbon intensity that varies by region (the grid mix: coal, gas, hydro, solar, wind, nuclear). The same workload in… 1 Group attachment Assigning a schedule, budget, or notification rule to a resource group so every member inherits it automatically, instead of re-attaching per resource. 2× Group metadata The descriptive fields (name, description, budget, tags) that organize a resource group so future engineers understand its purpose and cross-group policies can apply. 1 Grouped Account dropdown A multi-select filter on the Resources page that organizes cloud accounts by provider (AWS, GCP, Azure) so a large multi-cloud estate stays navigable past the point a flat… 1 Grouped Type dropdown The 380+ resource types fall into 9 categories. The Grouped Type dropdown organizes the type filter around these categories: 1 Growth rate The growth rate is the most-leveraged input to a top-down forecast. Getting it right matters more than any other single decision. 1
Hallucination An agent answering from its own reasoning instead of calling the available MCP tools, producing made-up numbers that do not match the actual data, which trust-but-verify… 1 Hardcoded safety A safety mechanism such as the database denylist embedded directly in application code rather than configuration, making it non-bypassable and auditable to guarantee protection… 1 Headline number The single key metric presented first in a report to leadership (for example cost-per-paying-user), followed by drivers and forecast, so the message lands in about a minute rather… 1 Headroom factor A safety multiplier (typically 1.3 to 1.5x for event capacity planning) applied over the calculated minimum capacity to buffer for scaling delays and demand spikes, set higher for… 1 Hidden costs Bottom-up forecasting reverses the top-down approach: each team forecasts their own needs, and the FinOps function aggregates the results into the org total. The strength is… 1 Hide vs Placeholder The split: ZopNight defines the security policy per widget; customer chooses how to render denied widgets (hide vs placeholder). 1 Higher-severity-wins The anomaly-detection rule that when percent-deviation and z-score methods disagree on severity, the higher level is reported, so no anomaly gets downgraded. 1 Historical accuracy The historical accuracy in #4 is the trust anchor. Without it, the band is just an assertion; with it, the band is calibrated. 1 Historical proportions Top-down forecasting starts with the org's total trajectory and allocates down to BUs and teams using historical proportions. It is the fast, low-effort method appropriate for… 1 Host network mode A Kubernetes configuration where pods use the host's network namespace directly instead of an isolated interface, a legacy pattern often correlated with older workloads and cost waste. 1 HPA (Horizontal Pod Autoscaler) HPA (Horizontal Pod Autoscaler) automatically scales pod replicas based on CPU, memory, or custom metrics. Beyond the autoscaling itself, HPA's history tells you about workload… 1 HPA pause/resume The mechanism where ZopNight pauses a Horizontal Pod Autoscaler during a scheduled off-period so scale-to-zero can drop replicas, then restores the HPA's active state on resume. 1 HPA stabilization window A Kubernetes parameter controlling the time window over which the Horizontal Pod Autoscaler averages metrics before scaling, preventing rapid oscillation between min and max… 1 HPA target The utilization percentage (typically 65 to 70 percent for CPU) the Horizontal Pod Autoscaler aims to hold by scaling replicas, where a target set too high causes latency during… 1 Hybrid account structure A cloud account layout that splits resources by both team and environment (for example team-A-prod, team-A-stage), giving the strongest isolation at the highest operational… 1 Hybrid forecast A cost forecast that combines top-down projections from the growth plan with bottom-up team estimates, reconciles the gap through discussion to surface assumptions, and commits to… 1 Hybrid model A commercial arrangement that combines two approaches, such as a FinOps team handling optimization breadth while a share-of-savings vendor specializes in commitment management. 1 Hybrid pattern The hybrid pattern handles mixed-workload scenarios. 1
IaC drift IaC drift = manual changes in the cloud console (or other tools) that diverge from what's in your Terraform/CDK/Pulumi. Drift breaks the "IaC as source of truth" promise. Without… 1 IaC tag enforcement Validation rules built into Infrastructure-as-Code CI pipelines that reject resource definitions missing required tags before deployment. 1 IAM role ZopNight connects to AWS via an IAM role with cross-account assume-role trust. The role grants the minimum permissions needed for each capability. The customer can grant or deny… 1 IANA timezone A cron without a timezone is ambiguous. ZopNight requires IANA timezone (e.g., Europe/London, Asia/Kolkata, America/Los_Angeles) so that: 1 Idempotency A property of an operation where running it many times has the same effect as running it once. ZopNight's remediation actions are idempotent: re-applying a stop action to an… 2× Idempotent remove The Remove lifecycle operation that safely repeats on failure, restoring cloud-side state to its pre-ZopNight configuration without partial corruption. 1 Identity Provider Single Sign-On lets users authenticate once against a trusted identity provider (IdP) and access ZopNight without managing a separate password. ZopNight supports three SSO… 1 Idle workload shape One of seven distinct Kubernetes idle patterns distinguished by replica state, traffic, CPU usage, pod state, suspension status, or endpoint backend presence. 1 Immutable template A preset dashboard configuration that cannot be edited directly; customization requires cloning it into a new saved dashboard before making changes. 1 Incident commander Cost incident commander: a single person responsible for coordinating response during a cost SEV-1 or SEV-2 incident. Borrowed from outage-response best practice; tailored for… 1 Incident communication cadence The structured message schedule during a cost incident, balancing urgency against noise through initial acknowledgment, periodic updates, resolution, and postmortem. 1 Indefinite-override hazard The risk that a time-bounded override forgotten after creation keeps running indefinitely, accumulating cost until someone notices quarters later. 1 Industry benchmark Comparable cost or carbon figures from peer companies or published averages that give context for judging whether an organization's position is favorable. 1 Inform Inform is the first phase of the FinOps lifecycle. It answers the question: who knows what about cloud spend, when, in what form, and with what action available? Most FinOps… 1 Infracost Infracost (or equivalent) is the pre-merge equivalent of drift detection, catches cost surprises early. 2× Infrastructure of infrastructure The "infrastructure of infrastructure" multiplied by team count = significant duplication. Centralization is the highest-leverage cost lever. 1 Instance Pool Pre-warmed compute that reduces cluster cold-start latency from 3 to 5 minutes down to 1 to 2 minutes by keeping ready-to-attach nodes available. 1 Inter-region transfer Data movement between geographically separate cloud regions that incurs bandwidth charges and must be counted in the total cost of a workload migration. 1 Internal billing ZopNight's allocation engine (the cost_allocation_daily table) is the source of truth for both surfaces. Reports → Teams shows showback by default; for chargeback, the same data… 1 isEstimated badge A confidence indicator on Event Readiness cost figures showing whether the number is calculated from pricing data (badge off) or a best-effort estimate given uncertain inputs… 1 ISO 27001 Pre-built compliance reports live at Settings → Compliance Reports: one-click generation for SOC 2, ISO 27001, quarterly RBAC review, and others. For framework-specific needs,… 1
K8s cost decoupling The architectural separation between cluster-level billing (the cost entity) and workload-level scheduling (the action entity), linked through labels for attribution. 1 K8s hierarchy The nested containment of Kubernetes resources as cluster, namespace, then workload type (Deployment, StatefulSet, CronJob), enabling quick navigation to any schedulable workload. 1 Kill-or-investigate The decision during a cost incident whether to stop a runaway workload immediately (when its trajectory is unsustainable) or diagnose first (when production dependencies exist). 1
Last Discovery timestamp A manual refresh takes 1–3 minutes for typical estates. The button is disabled with a spinner while a refresh is in progress. The Last Discovery timestamp updates when complete. 1 Last human operation The timestamp of the most recent manual change to a resource, drawn from CloudTrail or Activity Log, used to confirm that a stopped or idle resource is truly abandoned. 1 Layout The Cost Flow Sankey supports five preconfigured layouts, each cascading cost through different dimensions. Picking the right layout reframes the question being asked; switching… 1 Layout JSON The serialized structure storing a dashboard's widget arrangement, configuration, and sizing, which enables layout persistence and sharing across users via URL. 1 Layout switch reset The automatic clearing of drill-down navigation when the Cost Flow layout is changed, since drill paths depend on the cascade structure being switched. 1 LCU ELB. Per LB-hour ($0.0225 ALB, $0.0225 NLB) plus per-LCU (load balancer capacity unit) for traffic processed. A 24/7 ALB with modest traffic costs ~$22/month, small individually,… 1 Legitimate growth The most common real-world overrun: part legitimate growth, part waste. Decompose: 1 Lifecycle policy Every snapshot keeps billing forever until explicitly deleted. Lifecycle policies were never set. Result: snapshots of volumes that no longer exist, of databases that were… 2× ListCost Note BilledCost vs EffectiveCost vs ListCost. These are exactly the three bands from M0.1 L3 and M0.4 L4, normalized into the spec. 1 Live calculated cost What actually happened: the SaaS tool showed live calculated cost (rack rate), the invoice carried daily billing (post-discount). Both are correct. They answer different questions. 1 Live computation The concern with live computation is performance. Aren't aggregate SQL queries slow? 1
M&A tag collision The tag namespace conflict that arises when an acquired company's tag values (for example team=engineering) clash with the acquirer's existing values, forcing a migration strategy. 1 Management Group Azure organizes by Management Groups at the top, then Subscriptions under them. ZopNight assigns the service principal at the management group level for multi-subscription… 1 Manual action An immediate one-off start or stop that bypasses any attached schedule and requires explicit confirmation, used for incidents, ad-hoc demos, or unexpected capacity changes. 1 Manual refresh - Granted entries are re-attempted every cycle (~6h) - Denied entries are skipped for 24 hours by default: repeated AccessDenied calls cost time, and the underlying IAM policy… 2× Manual trigger A team sees MANUAL trigger at 15% over the last week. The most actionable next step: 1 Mark applied The "Mark Applied" button lets the customer note they've completed the action manually, so savings tracking works correctly. 1 Maturity model The FinOps Foundation uses a three-stage maturity model (Crawl, Walk, Run) to describe how a practice evolves. The model is not a ladder where each rung is unlocked sequentially.… 1 MAU Unit economics is cost per unit of business value. The denominator is the unit, the thing the business cares about producing or serving. Picking the right denominator turns "we… 1 Max override duration The Max Override Duration is a per-resource and per-resource-group setting (max_override_duration_minutes) that caps how long any single override on that resource or group can be… 1 MCP Model Context Protocol. Open standard for AI agent integrations. 1 MCP audit log The record of every MCP tool call in ZopNight, capturing user identity, PAT used, tool name, filters, response metadata, and status. 1 MCP configuration Setting up the ZopNight MCP server for Claude Desktop involves three steps: create a PAT in ZopNight, edit Claude Desktop's MCP configuration file, restart Claude Desktop. The… 1 MCP_DISABLED error The error returned when a PAT attempts an MCP connection while the organization's MCP toggle is switched off by an admin, rejecting all such attempts. 1 MCP-native By 2026, every cloud cost vendor claims "AI." Differentiation is in the specifics: MCP-native (engineer's own AI tool), read-only by design (CISO-friendly), open protocol (no… 1 Member list - Group detail page → Add Members: filter + multi-select - Member list → action menu: remove, move-to-group, attach-schedule, set-tag - Audit Log: every add and remove is recorded… 1 Meta-audit Audit-log queries that track who is accessing the audit logs themselves, used for security monitoring and compliance to detect unauthorized access to sensitive records. 1 Metadata enrichment The discovery step where per-service API calls pull detailed metadata (instance type, tags, IOPS, Multi-AZ status) to supplement the initial resource inventory. 1 Metrics drawer The Metrics drawer is the second-most-clicked surface on a recommendation card (after the savings line). It shows the cloud monitoring data the rule used: CloudWatch (AWS), Cloud… 1 MetricsAware The interfaces are composable: a rule can be just Rule (state-based), or Rule + MetricsAware, or all three. 1 Migration pilot An initial migration of a non-critical workload, typically 1 to 2 weeks, that validates latency, cost, and carbon impact before committing to a production migration. 1 Migration prompt - Unattached only hides resources already on a different schedule. A team should know when they're about to disrupt an existing attachment. - Not in any group hides resources… 1 Milestone Each milestone needs a single owner. A milestone without an owner is a wish. 1 Mixed routing Mixed routing requires application changes. ZopNight's RC-1603 recommendation provides the savings estimate and which model categories to route to. 1 ML cost driver A major cost contributor in ML workloads such as Bedrock inference, training compute, GPU instances, or provisioned throughput, each with its own optimization lever. 1 Mode auto-derivation Setting the autoscaling mode (monitor, recommend, or autopilot) automatically from the IAM credential's permission level, without manual configuration. 1 Model Context Protocol MCP, Model Context Protocol, is an open protocol that connects AI assistants (Claude Desktop, Cursor, Codex, Claude Code) to data sources and tools. It lets an AI agent call… 1 Model selection Choosing the cheapest model that still meets the quality bar for a task, and routing simpler prompts to cheaper models. Price gaps between tiers are large but finite: Claude Opus… 1 Model selection lever The optimization technique of routing each inference query to the right model tier by complexity (Haiku for simple, Sonnet for medium, Opus for complex) to cut per-token cost. 1 Modernization path Each recommendation includes the cost impact + suggested modernization path. 1 Monitor mode In monitor mode, any existing cloud-side autoscaler continues to do its own native scaling. ZopNight just doesn't touch it. ZopNight observes and provides recommendations. 1 Monitor-only database A database that Event Readiness does not auto-scale; instead it surfaces connection-pool and capacity recommendations for manual DBA action, given the higher risk of mutations. 1 Monthly close The "monthly close" rhythm is what gives the chargeback its operational shape. Quarterly closes look easier but lose visibility for too long; weekly closes create noise that… 1 Monthly cost review The recurring month-end meeting among team lead, finance partner, and FinOps lead covering variance, top drivers, forecast, and budget adjustments. 1 Monthly settled Monthly settled. The closed-out invoice. Provider may revise daily numbers retroactively as late-arriving metering events or reservation adjustments post. Final by the 5th–10th of… 1 Move-up action The first move-up action from Crawl is typically: 1 Multi-account Multi-account architecture is the practice of running workloads across several distinct cloud accounts (AWS accounts, GCP projects, Azure subscriptions) rather than one big shared… 1 Multi-approver pattern An approval-gate configuration requiring more than one approval before remediation runs, such as a two-person rule, any-of-team, or escalation chain for high-stakes changes. 1 Multi-cloud governance Multi-cloud governance is the practice of running cost discipline across these clouds without building three parallel governance pipelines. 1 Multi-cluster permission scoping Configuring IAM credentials per cluster so ZopNight cannot modify a cluster it lacks credentials for, preventing silent cross-cluster access. 1 Multi-org config A single AI tool (Cursor, Codex) configured to connect via MCP to multiple ZopNight organizations using different PATs and organization IDs. 1 Multi-org setup An AI tool such as Claude Desktop configured with multiple MCP server entries, each pointing to a different ZopNight organization with its own PAT and org ID. 1 Multi-source synthesis An AI agent's ability to chain several MCP tool calls across audit logs, costs, and recommendations, then combine the findings into one coherent answer. 1 Multiplier model The multiplier model is simpler. Often easier for non-engineers to think about. 1 Mutating action ZopNight's audit log captures every mutating action (POST, PUT, PATCH, DELETE) performed through the API or the UI (the UI sends API calls under the hood, so the distinction does… 1 MVT (Minimum Viable Tag set) The core set of four mandatory tags (team, environment, cost_center, owner) that enable attribution, policy routing, and chargeback without fragmenting governance. 1 MVT (Minimum Viable Tags) The core set of four mandatory tags (team, environment, cost_center, owner) that enable attribution, policy routing, and chargeback without fragmenting governance. 1
Name-confirmation Deleting a schedule requires name-confirmation (typing the schedule name into a confirmation field) to prevent accidents. The name-confirmation pattern is the same one used for… 2× Namespace boundary In the ZopNight Kubernetes hierarchy (cluster to namespace to workload), the namespace is the grouping and isolation layer within a cluster that you filter and scope schedules and… 1 NAT Gateway NAT Gateway on AWS is $0.045 per hour ($32.40 per month per gateway) plus $0.045 per GB data processed. Dev VPCs with one NAT per AZ across three AZs run $97 per month before any… 3× Net change threshold In redistribution suppression, the configurable percentage (default 20 percent) by which the aggregate cost across affected teams must move before team-level anomaly alerts fire,… 1 Net-zero commitment An organization-wide sustainability goal to reach net-zero carbon emissions by a target year, which cloud scheduling and carbon-aware decisions contribute toward and which anchors… 1 No backfill The K8s scheduler simply checks suspend before firing. Skipped times are gone forever, no backfill. 1 No clear cause The honest outcome the anomaly root-cause engine surfaces when it cannot attribute a cost spike to a confident single cause, instead of fabricating one, leaving the operator to… 1 Non-prod fallacy The non-prod fallacy is a specific commitment-design mistake that recurs at almost every organization in the first FinOps year: buying reservations or Savings Plans for… 1 noStop prediction An auto-tagging output that predicts, with a confidence score, whether a resource can be safely stopped, serving as the critical "is this safe to act on" signal that prevents… 1 Notification channel A webhook-based destination (Slack, Microsoft Teams, Google Chat, or any URL that accepts a JSON POST) configured under Settings to receive ZopNight notifications on schedule… 1 Notification routing The practice of subscribing each notification channel to a chosen subset of event types and severities, so the right alerts reach the right channel and alert fatigue is avoided. 1 Notification suppression The lever for tuning notification volume down without losing signal, using rules such as suppressing routine auto-remediation events by resource so that only events warranting… 1 Numerator The denominator (M4.3.L1) tells you what unit of value you are dividing by. The numerator is the dollar amount in the cost-per-unit calculation, and which dollars to include… 1 Numerator change log A dated record documenting any change to a unit-economics cost numerator definition, including the old and new scope and the recomputation of prior periods, so that cost-per-unit… 1
OAuth 2.0 An authorization framework (it grants access to resources), not an authentication protocol; the authentication layer built on top of it is OIDC. ZopNight supports OAuth-based… 2× Off-hours recovery The spend reclaimed by shutting non-production resources down outside working hours on a schedule, while keeping an on-demand or on-call wake-up path so the environment can be… 1 On-demand vs provisioned The choice between paying per-request on-demand pricing (scales with traffic, can spike) versus reserving provisioned capacity billed per hour (predictable, but over-pays during… 1 One-click apply A rule is only wired for one-click Apply once these checks pass; until then it stays advisory or guided. The allowlist (contract/autoremediation_allowlist.go) is the source of… 1 Open recommendation A recommendation that has been surfaced but not yet acted on, representing reclaimable spend that ZopNight sums into "reclaimable" savings figures and highlights in views such as… 1 Operate Operate is the third phase of the FinOps lifecycle and the one that separates organizations that get FinOps from organizations that ran a FinOps sprint once. Without Operate,… 1 Operate cadence "FinOps owns the operate cadence and the per-team numbers." This statement most directly violates: 3× Operate-led optimization An optimization model where cost work is sustained through a continuous weekly Operate cadence with clear ownership, contrasted with project-led sprints that end and leave savings… 1 Operating cadence ZopNight's onboarding includes a maturity self-assessment. Customers answer 8-10 questions; the system surfaces a maturity score and the top three gaps to address. For Crawl-stage… 1 Operational floor The correct framing: CDCR handles the operational floor. Architectural ceilings remain with engineering ownership. The right organizational structure has both: CDCR running the… 1 Optimize Optimize is the second phase of the FinOps lifecycle. There are exactly four levers. Every optimization initiative is some combination of these four. Ranking them by impact and… 1 Ordered scaling The ordered scaling can be slow. Plan for it. 1 Org overhead Shared or unallocated infrastructure cost that sits at the organization level in the budget pyramid, rolled into the org budget alongside the sum of business-unit budgets rather… 1 Org settings The organization-level configuration surface where admins tune platform-wide behavior such as notification severity routing and the default dashboard, with values cascading down… 1 Org Tree A ZopNight Reports view that visualizes the cloud estate's provider-side hierarchy (AWS Organizations, GCP folders/projects, Azure management groups/subscriptions) as a tree with… 1 org-ai-skills repo For new engineers: symlink the org-ai-skills repo on day 1. The library is part of the role's tool belt. 1 Org-level toggle A single admin-controlled switch (Settings, Org, API) that enables or disables MCP access org-wide, whose blast radius is bounded to MCP activity so disabling it leaves non-MCP… 1 Org-shared dashboard The V1 dashboard model where every saved dashboard is visible to anyone in the org, with no per-user private dashboards, and per-user flexibility limited to bookmarking a… 1 Organizational Unit Concepts: - AWS Organizations: the top-level container that owns multiple AWS accounts. - OU (Organizational Unit): a folder-like grouping of accounts. Service Control Policies… 1 Orphan storage In most production clusters, orphan storage = $500-$5,000/mo in waste. The cleanup is straightforward. 1 Oscillation pattern Rapid back-and-forth scale-up then scale-down of an autoscaler caused by too short a cooldown reacting to transient metric spikes, fixed by setting a cooldown (typically 120 to… 1 Over-commitment The "disaster" case is Scenario C. An RI bought for a workload that gets re-architected or migrated mid-term keeps billing the committed rate until expiry, on capacity nobody… 3× Overlap (schedule) A condition, visible on the 24-hour weekly grid, where redundant crons issue duplicate ON or OFF triggers for the same resource, which is non-destructive but noisy in the action… 1 Override Time-bounded suspension of a schedule's normal cadence. 1 Override + cluster The pattern of using the Override system to force-on a cluster (for example a Databricks cluster) for a few hours to handle an edge case, after which the schedule resumes when the… 1 Override archive The Overrides page "Expired" tab, a convenience record of historical overrides useful for audit, pattern detection, and cost reconciliation, distinct from the Audit Log which is… 1 Override scope The implicit fourth field of an override, determined by where it is set (an individual resource or a resource group), which governs the set of resources the override applies to. 1
P95 / P99 The 95th and 99th percentile of a metric's historical values, the "typical-high" aggregations that capture recurring peaks that averages miss and single spikes (max) overweight. 1 P95 target The autoscaling smart-default target value set at P95 minus 5 percent, chosen so scaling triggers before saturation but not during normal load, avoiding both latency risk from… 1 Parametrized skill A reusable prompt or Claude Code skill written with variable placeholders (team, time window) instead of hardcoded values, so one skill serves the whole org across many teams,… 1 PAT Personal Access Token. Read-only credential for API/MCP access. 3× PAT description This makes it easy to answer "which device made this call?", the PAT description identifies the device. 1 Pattern analysis SMART action items. Single ownership. Tracked weekly. Reviewed monthly. Pattern analysis quarterly. 1 Peak Hours preset A team applies the Peak Hours preset to their production EC2 fleet. They start seeing customer impact at 10:30 PM each day. Most likely cause: 1 Per-account sync Per-account sync status is in the Cloud Accounts page; if one account is failing while others are succeeding, only the failing account's resources are stale. 1 Per-audience framing Presenting the same cost data through the lens a specific audience can act on, such as ZopNight's Executive, Engineering, and FinOps dashboard presets, each a curated widget set… 1 Per-env account structure A multi-account model that splits cloud accounts by environment (dev, stage, prod) regardless of team, which suits smaller orgs and strong environment-level compliance but blurs… 1 Per-group budget A budget scoped to a resource group of multiple resources with coordinated ownership and lifecycle, whose threshold alerts land on the group's owner (often a team's tech lead). 1 Per-key coverage If you don't have visibility into per-key coverage, that's the first thing to fix. Without it, you're guessing which key is the bottleneck. 1 Per-org isolation The security property that each customer organization has a distinct credential namespace so one org's credentials cannot be queried, decrypted, or used by another org under any… 1 Per-region pattern A 30-minute design exercise. Per-region pattern often the right starting point. 1 Per-resource attribution Direct assignment of a cost to the single resource that incurred it, the simplest allocation case that anchors per-resource budgets on the owner who chose the resource's sizing. 1 Per-step delay Per-step delay specifies how long ZopNight waits after the previous resource is confirmed-started before starting the next. Useful for warm-cache scenarios, DB replication setup,… 1 Per-team account structure A multi-account model that splits cloud accounts by team across all environments, giving each team its own account for isolation and accountability at the cost of duplicating… 1 Per-team budget The total is the same spend; different budgets watch different slices. When db-prod-orders crosses 75%, only the DB team is alerted. The platform team's per-team budget is not… 1 Per-widget RBAC Some dashboard widgets surface data that not all users should see: audit logs, RBAC configuration, raw cost data scoped to other teams. Per-widget RBAC controls visibility on the… 1 Percent deviation method A magnitude-based anomaly detection method that computes how far a day's cost sits from its 7-day rolling average as (X minus Y) divided by Y times 100, mapping the result to… 1 Periodic-workload pattern A usage shape where a resource sits mostly idle but spikes on a recurring schedule (monthly batch jobs, weekly reports, quarterly runs), which average-based right-sizing rules… 1 Permission Visibility Per-cloud, per-region IAM audit. 2× Persistent disk GCP's block storage volume charged per GB-month across SSD and HDD tiers, and one option (as regional persistent disks) for replicating at the storage layer to avoid cross-zone… 1 Phased rollout A speculative approach to enabling write actions where capability is introduced in risk-ordered phases (starting from today's read-only Phase 0) only once pre-conditions and… 1 Pickup rate The percentage of surfaced recommendations that actually get remediated rather than closed as won't-fix, a core measure of the cost of detect-only tooling that rises sharply under… 1 Placeholder pattern Some widgets (Audit Log, RBAC Summary, Cloud Accounts) are typically Admin-only; PAT Inventory is SuperAdmin-only. The placeholder pattern means they can appear on a shared… 1 Pod-hours vs instance-hours Two decoupled time-accounting metrics in Kubernetes where pod runtime (the workload-level scheduling metric) is independent of node runtime (the cluster-level cost metric), so… 1 Pod-level attribution Rolling up pod resource usage to per-team or per-app cost via Kubernetes labels, so cluster-level cost can be assigned to the workloads that actually drive it. 1 PodAntiAffinity A Kubernetes scheduling rule that keeps replicas of a deployment on separate nodes, used to prevent multi-replica workloads from all landing on one node and losing their… 1 Policy entity One of the 15 fixed authorization objects in ZopNight's RBAC table that every protected endpoint maps to, where a role is a set of (entity, action) pairs the gateway enforces on… 2× Policy guardrail A configurable org-wide limit such as Max Override Duration that catches the canonical mistake, forever-overrides, without micromanaging legitimate ones, and serves as a… 1 Policy inheritance The model in which a Personal Access Token is user-scoped and carries exactly the user's RBAC policies, no more and no less, so the token can never do what its owner cannot. 1 Policy lifecycle The four idempotent, reversible operations on an autoscaler policy, Apply, Pause, Resume, and Remove, each mapping to specific cloud API calls under the hood. 1 Postmortem A postmortem is a written record of an incident, its root cause, and the action items that prevent recurrence. For cost incidents, postmortems follow the same structure as… 1 PR cost comment The output of a pre-merge cost estimation tool, posted on the pull request so reviewers see the monthly cost delta of an IaC change alongside the code diff, making cost a… 1 Pre-computed recommendations Recommendations evaluated on a cron cadence and stored in the database so the UI reads them instantly, trading roughly six-hour freshness for a sub-500ms read path that scales to… 1 Pre-destruction checklist Pre-destruction checklist for every destroy. Test in non-prod first. Backup + rollback plan. Document the why. Approve appropriately. 1 Pre-merge cost estimation Pre-merge cost estimation: a tool that calculates the cost impact of an IaC change BEFORE the change is merged. The output becomes a PR comment; reviewers see "+$400/month"… 1 Pre-scaling Pre-scaling cost is real but worth it for the customer experience. 1 Pre-warmed demo A demo-prod scheduling pattern that starts a demo environment about 24 hours before a scheduled demo and shuts it off afterward, recovering near-total cost between demos for… 1 Predictable event A traffic spike with a known time and magnitude, such as Black Friday or a product launch, for which Event Readiness can pre-scale infrastructure beforehand instead of relying on… 1 Predictive scaling refusal ZopNight's refusal to Replace a PredictiveScaling policy, because the raw spec captures the configuration but not the trained predictor model, so a restore would create a… 1 Preset Most schedules in production fall into three patterns. ZopNight ships three preset schedules that cover these patterns. Customers can use a preset as-is or as a starting point to… 2× Preventive enforcement A team with 4 MVT tags and preventive enforcement spends ~10 hours/year on tag governance. Without it, ~10 hours/week. 2× previous_config The prior cloud-side configuration saved on the policy event row during Apply, which ZopNight reads back to perform a safe rollback when a policy is removed. 1 previousConfig The existing configuration recorded at Adopt time, when ZopNight makes no cloud mutation, so the pre-existing setup can be restored later. 1 Pricing API The pricing data lives in public APIs: - AWS Pricing API: https://pricing.us-east-1.amazonaws.com/... - Azure Retail Prices: https://prices.azure.com/api/retail/prices - GCP Cloud… 1 PricingAware PricingAware is what gives the recommendation card its dollar figure. 1 Primary plus tactical A multi-cloud pattern where one provider carries 60 to 90 percent of spend and hosts new workloads while a smaller secondary cloud (10 to 40 percent) serves a specific driver such… 1 PrivateLink Quarterly network audit. Top 3 patterns: VPC endpoints, Transit Gateway, PrivateLink. Make cross-region decisions explicit per service tier. 1 Privileged container Not every privileged container is wrong: 1 Project-scoped MCP A Model Context Protocol server defined in a repository's .claude/mcp.json rather than the global config, so a specific team or project can connect Claude Code to dedicated cost… 1 Prompt caching A Bedrock technique that caches long repeated context such as system prompts or RAG templates across calls to cut input token cost by roughly 90 percent on the cached portion,… 1 Prompt injection Prompt injection against a read-only MCP: 1 Prompt scope The first required component of a team-specific prompt, stating exactly which resources, accounts, or tags apply (for example team=payment-team, accounts=prod-us, prod-eu) to fix… 1 ProsperOps Share-of-savings vendors (ProsperOps, Spot.io, etc.) manage cloud commitments and charge a percentage of the verified savings they produce. The model is "pay only when we save you… 1 Proven floor The "equivalent 24/7 instances" is what you commit on. That's the proven floor. 1 Provider default tags Tags applied automatically by an IaC provider block (such as Terraform default_tags or CDK Tags.of()) to every resource it creates, removing per-resource tagging boilerplate and… 1 Provider weighting By provider weight. A team that runs $1M on AWS and $200K on GCP is 80% AWS-weighted. The team's optimization attention should be 80% on AWS. Provider weighting prevents the "I… 1 Provisioned IOPS A cost added beyond baseline storage when I/O throughput is reserved in advance, measured in operations per second and common on RDS and io2 volumes, which can add significant… 1 Provisioned throughput The break-even point: roughly 70% utilization of provisioned throughput. 1 Provisioner The ZopNight backend component that orchestrates cloud API calls when an autoscaling policy is applied, handling auth, error mapping, and retries while preserving the previous… 1 Published vs realized discount The gap between a provider's headline discount rate and the discount actually achieved, computed as published discount times coverage times utilization, which usually lands well… 1 PUE Power Usage Effectiveness, the ratio of total facility power to IT equipment power, used in carbon math to account for cooling and infrastructure overhead beyond raw compute draw. 1 Pull API In practice: most customers start with CSV for backfill, then Push API for ongoing. A minority prefer Pull API for governance reasons. 1 Push API In practice: most customers start with CSV for backfill, then Push API for ongoing. A minority prefer Pull API for governance reasons. 1 PV (PersistentVolume) The actual persistent storage resource allocated in a Kubernetes cluster, which sits in Bound, Released, or Failed state and can be orphaned to keep accruing storage cost if not… 1 PVC (PersistentVolumeClaim) A request for persistent storage in Kubernetes that binds to a PersistentVolume, and which can be orphaned with no pod using it while still incurring storage cost until detected… 1 PVC preservation The behavior where PersistentVolumeClaims stay bound and their data persists when a StatefulSet scales to zero or is paused, so storage cost continues even though compute is stopped. 1
Quality-vs-cost tradeoff The explicit choice when optimizing ML spend, such as routing queries to a cheaper model like Haiku instead of Opus, to accept some risk of quality loss for large cost reduction,… 1 Quarterly business review An end-of-quarter strategic cost meeting with org leadership, FinOps leads, finance partners, and team reps to review cost trajectory, cost-per-unit trends, major initiatives, and… 1 Quarterly retrospective A quarterly review of all cost-related postmortems to find cross-incident patterns, confirm action items were completed, and measure the cumulative effect of corrective actions on… 1 Quarterly runbook A documented repeatable procedure run every quarter, such as PAT rotation across weeks 1 through 3, covering notification, execution, and verification steps that stay largely… 1 Query classification Categorizing incoming queries by complexity with a lightweight classifier, often Haiku itself, so each is routed to an appropriately sized model to cut cost while holding quality. 1 Quick Setup Quick Setup is a streamlined flow for the most common autoscaler scenario: pick a target, accept smart defaults, save. Three clicks. For Advanced cases (custom metrics,… 1
Rack rate Public, undiscounted unit price from rate cards. 2× Raise For each budget overrun, investigate and decompose. Document the raise + enforce decisions in the budget's notes. ZopNight's audit log captures the budget adjustment with reason… 1 Rate optimize The third of four optimization levers, using commitments (Reserved Instances, Savings Plans, Committed Use Discounts, Spot) or negotiated discounts to pay less per unit, sequenced… 1 Rate-as-of A USD/INR exchange rate today is 83.20. A year ago it was 79.50. Six months ago it was 81.10. A cloud bill in INR converted to USD using "today's rate" gives one answer; converted… 1 RBAC Role-Based Access Control. 15 policy entities. 1 Reactive autoscaling gap The roughly 5-minute window where a reactive autoscaler lags a traffic spike (traffic arrives, autoscaler triggers, instances launch, instances become ready) leaving customers… 1 Read-only contract The read-only contract is not a limitation; it's a feature for risk-averse organizations. 2× Read-only contract verification Testing a destructive query like delete resource X against the MCP connection to confirm the agent refuses and redirects to the ZopNight UI, proving the connection is genuinely… 1 Read-only MCP Across these scenarios, the answer is the same: read-only MCP is the right boundary; alternative surfaces handle the writes. 1 Read-only safety The answer is the read-only safety model with scoped writes. The architecture is: 1 Realism discount A team has $80K monthly non-prod compute spend. Standard schedule (8-8 M-F), realism discount 0.7×. Realistic monthly savings: 1 Realism factor The numbers are computed from the schedule's crons (active hours per week), the attached resources' rack-rate cost (from the pricing API, live), and a configurable realism factor. 2× Realization rate A team's monthly realization rate is consistently 70%. Best action: 1 Realized savings The math says scheduling saves 64 percent. A team that has scheduled non-prod sees only 28 percent realized savings. Most likely cause: 2× Reason field Treat the reason field like a commit message. Future-you (or the next engineer on call) will thank present-you for the context. 2× Recent Activity tab The Recent Activity tab in the evidence panel shows operations against the resource, pulled from CloudTrail (AWS) / Cloud Logging (GCP) / Azure Activity Log via the daily… 1 Reclaim policy A PV with reclaim policy "Retain" after its PVC is deleted: 1 Reclaimable The Cost Flow Sankey has an optional savings overlay that highlights flows with reclaimable spend (open recommendations) and a separate unattributed teams overlay that highlights… 1 Recommend mode The middle tier of autoscaling autonomy where ZopNight surfaces scaling suggestions in the UI and the customer clicks Apply on each one, adding an approval gate before any scaling… 1 Recommendation card The recommendation card is the unit of action. Every field exists to support one of three decisions: apply (do the thing), dismiss (this doesn't apply), or snooze (revisit later).… 2× Reconciliation The 7-day reconciliation gives full picture; 30-day trend confirms patterns. 2× Reconstructibility check The reconstructibility check is the safety gate. Some configs can't be perfectly restored; ZopNight refuses to take risk. 1 Reconstructibility refusal ZopNight's refusal to Replace an autoscaling policy when byte-accurate restoration on Remove cannot be guaranteed, specifically policies with predictive scaling, step adjustments… 1 Red diagnosis The investigation path for an overrun budget: open the budget detail, find the inflection point in Cost Trend, cross-reference the Cost Flow Sankey for the dominant dimension,… 1 Redacted field A sensitive audit log value replaced at storage time with a mask such as [REDACTED] or a partial like 1234 for tokens or jane@example.com for email, applied irreversibly for… 1 Redaction Before any body is written to the audit log, a redaction middleware scans for known-sensitive fields and replaces them with [REDACTED] (or a partial-mask equivalent). The… 1 Redirect URI The URL registered with an OAuth provider such as Google or GitHub where the provider sends the user back after authentication (for example… 1 Redis Stream A per-organization ordered log transport that captures mutating API calls in real time with microsecond precision, buffers them for about a minute, then syncs to MySQL for durable… 1 Redistribution suppression Redistribution suppression worked: kept attention on the real signal. 1 Region carbon intensity The grams of CO2 emitted per kilowatt-hour of a cloud region's grid, ranging from around 30 in hydro-powered regions to roughly 700 in coal or gas regions, used to pick… 1 Relative time display - Target: the resource or group the override applies to - Type: Force-on or Force-off - Reason: the documented reason (full text) - Expires: relative time display ("in 2 days,"… 1 Reliability theatre Reliability theatre = investments that LOOK like reliability but don't actually provide it under failure. Paying for "HA" features that don't help when the failure happens. The… 1 Reliability tier A workload classification (typically Tier 0 revenue-critical through Tier 3 dev/test) that maps to SLO targets and decides whether reliability investments like multi-AZ,… 1 REMEDIATION_NOTIFY_TERMINAL A team enables REMEDIATION_NOTIFY_TERMINAL = true. Most likely after a month they will: 1 Reorg-proof tag A tag value that abstracts away from org structure, such as team=marketing-acquisition for the function rather than a dated or person-named value, so it survives reorganizations… 1 Replace flow The Replace flow is safe in practice. The reconstructibility check + saved config + idempotent restore handle the failure modes. 1 Replica count math The reliability exponential where one pod gives about 99.9 percent uptime, two independent pods reach about 99.9999 percent for roughly 2x cost, and a third pod adds diminishing… 1 Report-and-ticket The pattern CDCR replaces is older than cloud. Call it report-and-ticket: 1 Request body capture Recording the full JSON request payload of a POST, PUT, or PATCH call in the audit log for forensic reconstruction, with sensitive fields redacted before the body is persisted. 1 Required policy The widget registry is in code; each widget exports its required policy. The dashboard renderer reads the user's policy set and decides per widget. For new widgets, the policy… 1 Reserved Instance A cloud commitment for a specific instance family and type bought on a 1 to 3 year term, saving roughly 30 to 40 percent below on-demand at the low end (1-year, no-upfront) and up… 2× Resource drill-down Navigating the Kubernetes hierarchy in ZopNight from cluster to namespace to workload type to a specific workload, typically three clicks from the estate-wide view to a single… 1 Resource Explorer 2 Resource Explorer 2 (RE2) is AWS's canonical multi-region, multi-service inventory API. A single Search call returns resources across services in one response. ZopNight uses RE2… 1 Resource Graph Azure Resource Graph is Azure's canonical inventory query API. ZopNight runs an expanded query that covers 101 resource types in one request: 1 Resource group A resource group is a named bundle of cloud resources. Once a schedule (or budget, or notification) is attached to a group, every member of the group inherits the attachment.… 1 Resource limit The maximum CPU or memory a Kubernetes pod may consume, above which it is CPU-throttled or OOM-killed, and which should sit near p99 actual usage plus a 30 to 50 percent buffer to… 1 Resource request The minimum CPU or memory reserved for a pod when it is scheduled, guaranteed to the pod and setting how many pods fit per node, making it the primary lever for Kubernetes cost… 1 resourceIds This is the most common state in mid-size customer orgs. The resourceIds list is computed at request time from team membership, tags, and resource-group assignments. The user does… 2× Response body capture Storing the full JSON response returned by a mutating API call (POST, PUT, PATCH, DELETE) in the audit log with sensitive fields redacted at storage time, enabling forensic… 1 Restore window The 30-day period after a resource group is soft-deleted during which it can be recovered with members and attachments intact, after which the group is permanently purged. 1 Review cadence The data refreshes daily; the review cadence is weekly/monthly. Don't conflate the two: daily updates with monthly review is the typical pattern. 1 RI exchange AWS's ability to swap a Reserved Instance of one type for another, such as m5.large to m6i.large, to recover value when architecture changes leave the original RI mismatched to… 1 RI marketplace AWS's resale platform where customers can sell unused Reserved Instances mid-term, typically at a 10 to 20 percent loss, rather than holding stranded capacity until expiry. 1 Right-sizing Right-sizing requests is often the single biggest K8s cost lever. 1 Right-sizing throughput Tuning Bedrock provisioned throughput to match actual usage, typically sized at average load rather than peak and paired with on-demand for bursts, to minimize cost while holding… 1 Rightsize Why third, not first: commitments only pay back on workloads you actually run for the full term. Committing to capacity you then schedule off is a value-destroying move. The right… 1 ROI framing Presenting Event Readiness cost next to expected revenue impact, for example $5K cost against $80K of protected revenue for 16x ROI, to justify approval to Finance on value rather… 1 Role consolidation The fix is role consolidation reviews, typically quarterly: 1 Role description A one-paragraph field on a custom role that records the job to be done, the policies included, and the rationale, so a future reviewer understands intent and role proliferation is… 1 Rolling test environment Rolling test environment: a test environment that scales up for each test run, then scales down. Replaces the always-on test cluster that idles most of the week. 1 Rollup Cost aggregation from the leaf level (account, project, or subscription) upward through a cloud hierarchy such as an AWS OU, GCP Folder, or Azure Management Group, producing… 1 Root cause analysis Investigate an anomaly using root cause analysis: 1 Root cause vs symptom The postmortem distinction between the underlying system failure (root cause, such as a cleanup script that hid its failures) and the surface event (symptom, such as an engineer… 1 RPO DR (Disaster Recovery) cost scales steeply with how fast you must recover and how little data you can lose. The framework: define RTO (recovery time) and RPO (recovery point) per… 1 RTO DR (Disaster Recovery) cost scales steeply with how fast you must recover and how little data you can lose. The framework: define RTO (recovery time) and RPO (recovery point) per… 1 RTO / RPO Recovery Time Objective, how fast recovery must happen, and Recovery Point Objective, the maximum tolerable data loss, which together set backup frequency and retention (tighter… 1 Rule category One of eight groupings of ZopNight's rule library (idle, rightsizing, schedule, orphan, compliance, discount, security, reliability, governance) that cluster findings by… 1 Rule-based prediction The auto-tagger's deterministic approach combining signals like naming patterns, existing tags, instance config, group membership, and account context into a composite score with… 1 Run stage The FinOps maturity level where a weekly Operate cadence drives continuous incremental optimization so savings compound quarter over quarter instead of decaying. 1
Safe rotation order The five-step PAT rotation sequence of generate new, update client config, restart client, verify new works, then revoke old, so the agent does not break if the new credential is bad. 1 Safe-to-auto A classification in the CDCR (Continuous Detect, Continuous Remediation) graduated authority model marking findings such as idle resources, orphans, and scheduled operations as… 1 Safety margin The safety margin absorbs uncertainty. Too small and forecasts miss; too large and budgets become slack. 1 SAML Security Assertion Markup Language. Enterprise SSO. 1 SAML 2.0 Any standards-compliant SAML 2.0 IdP should work. The "tested, documented" label means ZopNight has step-by-step instructions; uncommon IdPs may require reading the SAML spec. 1 Sanity band The sanity band clamps savings fractions to [0.05, 0.85]. Why: 1 Sankey diagram An interactive multi-column cascade that visualizes cost composition flowing from one dimension to another (for example Provider to Account to Type to Team), where node size… 1 Save-on-stop The save-on-stop is what makes the cycle reliable. 1 Saved search A named, reusable audit-log query saved in ZopNight so a recurring forensic or compliance question (such as "all RBAC changes this week") can be re-run against live data with one… 1 Savings decay The defining feature of Walk is savings decay: gains achieved in a sprint silently erode in the months that follow. 1 Savings estimator After resources are attached to a schedule, the schedule detail page displays a savings estimator. It computes the expected monthly savings from running the schedule on the… 1 Savings overlay The Cost Flow Sankey has an optional savings overlay that highlights flows with reclaimable spend (open recommendations) and a separate unattributed teams overlay that highlights… 1 Savings Plan AWS flexible commitment instrument. 2× Scale-to-one For workloads that can't fully stop (have weekend traffic, stateful caches, quorum constraints), but can run lean: scale-to-one. Keep one minimal instance running on weekends;… 1 Scale-to-zero A 15-minute exercise builds confidence in scale-to-zero. 2× Scaling action A scaling action's "trigger" field shows CPU 78%, target 60%. The interpretation: 1 Scaling policy A scaling policy tells the cloud's autoscaler when to add or remove capacity. ZopNight manages four target types: AWS ASG, AWS ECS service, Azure VMSS, GCP MIG. 1 ScalingLimited condition The HPA state where the autoscaler wants to add replicas but cannot, typically because it has hit its configured max, which is the strongest signal that a workload is… 1 Scenarios ZopNight's Unit Economics report includes a forecast overlay using driver-based methodology by default. The customer can override with extrapolation or import scenarios from a… 1 Schedulable resource A resource whose runtime does not need to be continuous (such as non-prod compute) and can therefore be started and stopped on an environment schedule, where most teams find 50 to… 1 Schedule Cron-based rule for starting/stopping resources. 1 Schedule attachment For many resources, the bulk action surface from M1.2 L4 extends to schedule attachment: 1 Schedule trigger A history-log entry showing a state change (Stopped to Running or the reverse) caused by an automated ZopNight schedule rather than a person, and the expected dominant pattern for… 1 Schedule-eligibility For each workload class: identify schedule-eligibility, deploy schedules where applicable, observe 60+ days, commit on the proven floor. ZopNight's Commitment Optimizer can… 1 Scheduling The arithmetic of scheduling is unforgiving and arrives at one number. 1 SCIM The provisioning protocol, well-supported over SAML, that lets an enterprise IdP automatically create, update, and deactivate ZopNight users so account lifecycle is managed centrally. 1 Scope drift The gradual, undocumented change in how a unit-economics numerator is defined over time, which invalidates trend analysis because a percentage improvement is only meaningful if… 1 Scope state The first question to ask: which scope state is this user in? Settings → Users → user detail → Effective Scope shows the state explicitly. The diagnosis flow: 1 Scoped filter A dashboard or view filter constrained to a specific team or slice of the estate, used to give each cloned per-team dashboard its own team-bounded data. 1 Scoped write A narrow, auditable, opt-in write action (like start or stop a VM, terminate a specific orphan) that does exactly one thing and nothing else even if the underlying credentials… 1 Secrets manager integration Storing agent and MCP credentials such as PATs in a dedicated secret store and having clients pull them from there, enabling automated rotation instead of hardcoded tokens. 1 Security-cost correlation The observation that some Kubernetes security configurations correlate with cost and reliability problems, so auditing security signals surfaces workloads that are both a risk and… 1 Sequence rule The commitment-design discipline that says schedule first, then observe the post-schedule baseline, and only commit to that reduced floor, so you do not over-commit to capacity… 1 Sequenced execution Sequenced execution lets a group specify an ordering: storage tier first, compute tier second, app tier third (for start); reverse for stop. 2× Service Account (GCP) A GCP identity granted the organization-viewer role at the org level so ZopNight can discover all projects automatically, authenticated via Workload Identity Federation… 1 Service Control Policy An AWS guardrail attached at an Organizational Unit level that applies to every account beneath it, for example forbidding a region across all accounts in a production OU. 1 Service dependency handling The practice of preventing breakage when a scheduled resource is depended on by another service, resolved either by scheduling the dependent services together as a group or by… 1 Service principal An Azure AD application identity used to authenticate a non-human client, granted a role at the tenant or management-group level so ZopNight can discover the subscriptions in… 1 Service Principal (Azure) The Azure AD application registered with Reader role at the tenant or root management-group level, connected to ZopNight with tenant_id plus app_id plus secret, so ZopNight… 1 ServiceName - The set of columns (about 50 in FOCUS 1.0: BilledCost, EffectiveCost, ServiceName, ResourceId, RegionId, RegionName, ChargePeriodStart, etc.) - The data types and allowed values… 1 Session permissions A user's resource scope computed at login and cached for the session lifetime (typically 8 hours), so team-membership or role changes take effect only on the next session refresh… 1 Session token The ZopNight frontend uses a single hook, usePermission(), to decide whether to render an action. The hook reads the policy set encoded in the user's session token, checks against… 1 Severity Severity is the lever for routing notifications correctly. Three levels (INFO, WARNING, CRITICAL) drive what channel an event goes to, whether it pages someone, and how often the… 1 Severity ladder Five severity levels, each tied to an action timeline. The severity ladder is the noise filter: without it, every finding looks equal; with it, attention goes to what matters. 1 Severity override A per-event-class setting that replaces the default severity for a specific case, for example downgrading a dev-environment cost anomaly to warning or escalating a… 1 Severity routing Using an event's severity level (INFO, WARNING, CRITICAL) to decide its destination channel, whether it pages, and how often the team should expect it, so the right audience gets… 1 Severity tuning Adjusting the severity assigned to a rule or finding to reduce noise, so that only findings warranting real attention are escalated and low-impact ones stay quiet. 1 Severity-vs-urgency The distinction between severity, ZopNight's classification of an anomaly's magnitude, and urgency, the team's interpretation of business impact, which is why the same severity… 1 Shape 2 (no traffic) The idle-workload shape where Kubernetes pods are running with replicas but receive no inbound traffic, meaning they are costing money while doing no work, including stale pods… 1 Share-of-savings Share-of-savings vendors (ProsperOps, Spot.io, etc.) manage cloud commitments and charge a percentage of the verified savings they produce. The model is "pay only when we save you… 1 shareCount When a resource has a single team owner, attribution is trivial. The tag tells you who. The hard cases are shared resources: load balancers, databases, Kubernetes clusters,… 1 Shared services account Shared services account: a dedicated cloud account for infrastructure used by multiple teams. The opposite of every-team-runs-their-own-Prometheus. Centralized; managed by a… 2× Shared tagging module A reusable IaC module (for example a Terraform tagged_resource module) that larger orgs adopt to enforce consistent required tags across resources rather than tagging each… 1 Shared-services allocation The chargeback approach for costs that benefit multiple teams (such as shared DNS or overhead accounts), commonly charged to a shared-services team that owns the overhead and then… 1 Shared-services team This pattern has two advantages over multi-team-tagged shared resources. First, clarity: the cost is attributed to one team that has explicit ownership. Second, incentive… 1 Showback Cost attribution to teams without billing transfer. 3× SIEM For compliance use cases, a specific routing pattern delivers events to a SIEM or audit channel without depending on humans to read them: 1 SIEM export Weekly MCP audit review (10 minutes). SIEM export for long-term retention. Alert on the documented anomalies. Quarterly compliance report. 2× SIEM integration Forwarding ZopNight's audit log to a security information and event management platform such as Splunk, Datadog, or Sumo Logic, typically via a scheduled job that pulls the… 1 SIEM webhook A notification route that mirrors the full audit log to a SIEM for compliance evidence collection, used by regulated organizations that need a complete record of remediation activity. 1 Signal weight The confidence value assigned to each individual auto-tagger signal (naming patterns, existing tags, configuration, resource group, account context), combined in composite scoring… 1 Silent overwrite When ZopNight encounters a target (ASG, VMSS, MIG, ECS service) that already has cloud-side autoscaling configured, two paths exist: adopt the existing configuration as-is, or… 1 Simplification sprint Run a quarterly chargeback complexity audit. Track rule count, dispute volume, close duration, and engineering time. If trends are bad, plan the simplification sprint, usually 1-2… 1 Single ownership SMART action items. Single ownership. Tracked weekly. Reviewed monthly. Pattern analysis quarterly. 1 Single-fire-per-period The single-fire-per-period rule prevents alert spam. A budget at 105% for two weeks fires once, not daily. The next conversation triggers at the next threshold (110%) or at… 1 Single-replica deployment Single-replica deployment: 1 pod, no redundancy. Lowest cost; lowest reliability. The right choice depends on the workload's environment + criticality + restart tolerance. 1 Size-scaling pattern A Databricks SQL warehouse schedule that runs a larger size during business hours and scales down to a smaller size overnight for occasional queries, best for prod with diurnal… 1 Skeleton crew The off-hours pattern of scaling a service down to a single replica (not zero) to keep it warm and reachable at minimal cost. A single replica does NOT preserve quorum: quorum… 1 Skill (Claude Code) A markdown file that Claude Code loads as a named command, letting a team invoke an embedded prompt by name so the same instructions run consistently every time, shifting prompts… 2× Skill changelog The dated list of version entries kept in a shared skill's metadata that records what changed in each release, including breaking changes, so users can see how the skill has evolved. 1 Skill deprecation The graceful retirement of a shared skill that has become obsolete (for example after an MCP tool is renamed or an output format changes), done deliberately rather than by silent… 1 Skill discovery How team members find shared skills to use, best served by a central, discoverable location (such as an org skill repo) so there is one place to look and duplication is reduced. 1 Skill frontmatter The YAML metadata block at the top of a skill file, delimited by triple dashes, holding fields like the one-line description shown in the menu and any parametrized args with their… 1 Skill maturity model The Level 0 to 6 roadmap for a team's skill library, from ad-hoc prompts (0) through personal, project-scoped, team-scoped, and org-wide repos (1 to 4) to CI testing with drift… 1 Skill quality gate The PR-review checklist a shared skill must pass before adoption (does it work as described, is the description clear, are parameters documented, is output consistent, are edge… 1 Skill sharing Choosing the right distribution mode for a skill, project-scoped in a repo, team-scoped in a per-team library, or org-wide in a single source of truth, and migrating from personal… 1 Skill versioning Tracking a shared skill's revisions with metadata and a dated changelog (including breaking-change markers) plus a quarterly review cadence, so users know what changed and can… 1 Skills (Claude Code) Claude Code's feature of custom reusable command files that, combined with the ZopNight MCP server, turn recurring cost workflows into parameterized team commands invoked by name. 1 SKU ladder The catalog-diff pricing path (SKURates) the recommender uses when savings come from changing what you use rather than how you pay, as opposed to the commitment math path (TierRates). 1 SKURates RC-156: gp2 → gp3 migration (SKURates path): 1 SLA Production budget at 90% with no SLA defined: 2× SMART action item A cost-postmortem follow-up written to be specific, owned by a single named person, and due-dated, since vague items rot while SMART items get done and prevent the same incident… 1 Smart defaults Smart defaults are statistical. They miss workload-specific context: 1 Smoke test A failing smoke test means: don't use agent-reported numbers in leadership presentations this week until fixed. 1 Snapshot The Idle EC2 rule (RC-001) computes savings using the full cost (compute plus storage plus snapshot), not just the EC2 row. The savings amount you see on the recommendation card… 1 SOC 2 Pre-built compliance evidence packages live in Settings → Compliance Reports. One click generates a CSV/JSON bundle for a specific framework + time window. Internally, each report… 1 Soft delete The recoverable delete lifecycle operation for a resource group, one of create, edit, soft-delete, and restore, so a removed group can be brought back rather than being… 1 Software Assurance A discount that the other clouds do not have. If you own on-premises Windows Server or SQL Server licenses with active Software Assurance, you can bring those licenses to Azure… 1 Source field The wizard's adopt-or-replace prompt is on every Create flow for an autoscaler policy. The source field shows on every policy's detail page. 1 Spot Discount via interruptible instances (50-90% off). 1 Spot burst A hybrid capacity pattern that commits to a base floor and uses spot or preemptible instances for stateless work above that floor, chosen when there is bursty demand and the… 1 Spot instance Deeply discounted compute (50 to 90 percent off) offered without a commitment but subject to eviction on about two minutes notice, fit only for stateless or interruption-tolerant… 1 Sprint-led optimization The Walk-stage operating pattern where a team runs one or two optimization sprints a year and achieves real savings that then decay over the following 6 to 12 months, contrasted… 1 SQL Warehouse Pattern A (schedule off-hours) for a SQL Warehouse provides: 2× SSO failure categories The four root-cause buckets that account for about 95 percent of SSO login failures (certificate, metadata drift, clock or timing, and user-side), which you classify first and fix… 1 SSRF guard The SSRF guard means customer endpoints must be on the public internet (or behind a public load balancer or API gateway). Internal-only endpoints (say, a service inside the… 1 Stable membership Groups solve one main problem: stable membership against evolving estates. 1 Stale data "Don't act on stale data" most directly motivates: 1 State history A "drift" entry in the state history means: 1 State surgery Direct manipulation of IaC state (such as terraform state mv or import) that changes tracking without touching cloud resources, a moderate-risk operation where you must verify it… 1 StatefulSet StatefulSets are like Deployments but with pod identity guarantees: pods are ordered (sts-0, sts-1, sts-2) and bound to persistent storage via VolumeClaimTemplates. Scaling a… 1 StatefulSet checklist The safety checklist for scheduling a StatefulSet, which requires confirming that PVCs are non-critical or backed up and accounting for pod ordinal identity and per-pod persistent… 1 Stddev-based cooldown The autoscaling default derived from Welford's online standard-deviation computation over a target's historical metrics, part of the smart-defaults recommendation for min, max,… 1 Step adjustment limit The Replace-flow refusal threshold that blocks migration of a step-scaling policy with more than two step adjustments, because that raw spec does not reliably round-trip. 1 Storytelling structure The four-section narrative (What happened, Why, What's next, and the Ask) used to translate unit economics for non-engineering audiences, leading with a single headline number and… 1 Stranded commitment A cloud commitment that no longer matches usage and has become a sunk cost rather than a saving, remediated where possible by exchanging it, selling it on, or letting it expire. 1 Structural fix A permanent, one-time change to process, data model, cadence, or ownership that resolves an anti-pattern at its root, as opposed to exhortation ("try harder") which produces brief… 1 Structural gap A persistent pricing-data gap that will not auto-resolve, typically caused by an unusual region and SKU combination missing from public price endpoints, requiring engineering… 1 Stuck job A process that consumes resources continuously on a single machine without completing (roughly 7 percent of cost anomalies), diagnosed by steady high consumption from one resource… 1 Sunk-cost trap The cognitive bias where over-commitment on reservations creates stranded costs that are hard to unwind, leading teams to keep paying for unused committed capacity instead of… 1 Suspend pattern A Kubernetes-native way to pause a CronJob by setting spec.suspend=true, which is non-destructive and instantly reversible, skipping scheduled executions while preserving… 1 Suspended CronJob A Kubernetes CronJob with spec.suspend=true that will not fire on its schedule, one of the idle workload shapes, which may be intentional (scheduled off by ZopNight) or forgotten… 1 Sustainable practice The compounding FinOps operating model achieved at the Run maturity stage, where a weekly Operate cadence makes savings build on prior quarters rather than decay, verified by… 1 Sustained-use discount GCP automatic discount for long-running compute. 2× Sync-back Default: sync-back ON. Most teams want consistency between ZopNight and cloud. 1 system error A remediation failure class where a cloud API returned an unanticipated or unsupported state (for example a cluster requiring manual console deletion), flagged as a red alert with… 1 System role A user with the Editor system role can still be team-scoped so they only have Editor permissions within a specific team. The role defines what actions are possible; the team scope… 1 Systematic bias Bottom-up forecasting reverses the top-down approach: each team forecasts their own needs, and the FinOps function aggregates the results into the org total. The strength is… 1
Tabletop exercise Run a tabletop exercise monthly: pick a recent anomaly, walk through the matrix step-by-step, identify gaps, revise. 2× Tag The fix is tag policy as code, enforced at provision time (Terraform / CDK / Pulumi pre-commit hook) and audited continuously (the Auto-Tagging service flags drift; see T2.M2.8). 1 Tag attribution Tag attribution is the flexible attribution dimension. Where team attribution maps cost to ZopNight's team concept (a first-class entity in the product), tag attribution maps cost… 1 Tag coverage - Reports → Teams splits spend by the team tag (and shared services by share count). The Unattributed bucket appears as its own row. - Reports → Tags lets any tag key… 3× Tag Coverage widget The Tag Coverage widget on the dashboard shows: 1 Tag debt Tags accumulate over time. Without governance, tag inconsistencies, value drift, and dead tags become entrenched. Like technical debt in code, tag debt compounds: every quarter… 1 Tag drift Tag drift trending upward over time suggests: 2× Tag inheritance Tag inheritance: parent-scoped tags propagate to children. Saves explicit tagging on every child resource and reduces the chance of drift. The pattern: set the tag once at the… 1 Tag migration pattern A process for updating tag values during reorgs, mergers, or structural changes while preserving cost attribution, covering rename (1:1 value mapping) and split (one value becomes… 1 Tag precedence The priority order applied when tag values are inherited from multiple scopes, where a resource-level tag overrides provider defaults and parent-inherited values, allowing… 1 Tag taxonomy Before deploying tag attribution at scale, the customer benefits from a tag taxonomy, a documented list of allowed keys and value patterns: 1 Tag-based membership A grouping pattern where resource-group membership is determined by matching resource tags (for example team=payment-api), letting a single schedule apply across multiple clusters… 1 Tag-selector group A resource group that spans multiple cloud accounts and is defined by tag selectors, so a single schedule attached to the group applies coordinated scheduling across those accounts. 1 Tags-as-code Treating tag policy as versioned code (for example tag-policy.yaml) with CI enforcement, review cycles, and automated drift detection, preventing tag debt the same way… 1 Team authority If you're contemplating chargeback because of a single failing test, fix the root cause first. Chargeback rarely fixes the underlying issue (lack of leadership review, lack of… 1 Team scope A role answers the question "what actions is this user allowed to take?" A team scope answers a separate question: "which resources are those actions allowed on?" The two are… 1 Team-level anomaly A cost anomaly detected at the team dimension, subject to redistribution suppression so that cost merely shifting between teams without a net org-level change does not generate noise. 1 Team-level ownership The hardest part of Crawl → Walk is not technical; it is mindset. The org has to stop treating cost as "finance's problem" or "FinOps's problem" and start treating it as… 1 Team-specific prompt A general prompt: "show me my cost." A team-specific prompt: "show me payment-team's variable cost this week vs same week last month, exclude the ml-training resources (they're… 1 Tenant cascade The cascading edge-case handling for dashboard ownership, where deleting an org clears its default_dashboard_id, deleting a default dashboard forces reassignment first, and a… 1 terraform destroy A destructive Terraform command that deletes cloud infrastructure (optionally scoped with -target), carrying extreme production blast radius and requiring a pre-destruction… 1 Terraform plan A zero-risk, dry-run Terraform command that previews the changes an apply or destroy would make without touching cloud state, used to map blast radius before acting. 1 Test utilization The percentage of hours per week a test environment is actively running tests, where low utilization (under about 30 percent) signals strong fit for rolling test environments that… 1 The three tests Two orgs at different scales, both passing the three tests with showback: 1 Theoretical savings - Schedules → Savings Estimator computes theoretical savings per schedule before saving. - Reports → Savings Trend computes realized savings (rack rate of saved hours). - Reports… 2× Threshold Each threshold fires once per period; the next threshold is the next conversation. The chain pattern is what turns budget management from a single end-of-month event into a… 1 Threshold alert A budget alert that fires when spend crosses a configured percentage (50, 75, 90, 100, 110), acting as a conversation trigger that notifies humans to decide a response rather than… 1 Tier (resource) A classification level in sequenced resource-group execution (Tier 1 storage and databases, Tier 2 compute, Tier 3 application and orchestration) that sets start order and the… 1 Tiered reliability A framework that matches reliability spending to business impact by assigning services to distinct SLO tiers (single-region 99 percent through active-active 99.999 percent), each… 1 TierRates Pricing data for commitment math. 1 Time-of-day filter A per-channel notification routing filter that limits delivery to specified windows (for example business hours on one channel, 24/7 for on-call), reducing alert fatigue by… 1 Time-to-remediation Every step is friction. The detector is fast (24h cadence at worst). Steps 2 through 8 routinely take 30 days or more. Even with a strong FinOps team, the realized… 1 Tool call A single MCP invocation by an AI agent against ZopNight's API, logged in full in the audit trail (tool name, filters and parameters, result) to enable security monitoring and… 1 Top 10 cap A noise-reduction limit that caps anomaly notifications at the top 10 resources per org, per dimension, per detection run, while additional anomalies stay visible in the feed… 1 Top-down forecast The growth rate is the most-leveraged input to a top-down forecast. Getting it right matters more than any other single decision. 1 Trace ID The trace ID is the key. Without it, support has to search across logs by timestamp, which is slow and ambiguous. 2× Traffic-light signal Budget health surfaces as a traffic-light signal (green, yellow, red) visible at a glance on dashboards and reports. The signal compresses three properties (actual spend, budget… 1 transient error A temporary cloud API error (rate limit, 5xx, eventual consistency) that resolves on retry, which ZopNight auto-retries with exponential backoff up to three times with no customer… 1 Transit Gateway Quarterly network audit. Top 3 patterns: VPC endpoints, Transit Gateway, PrivateLink. Make cross-region decisions explicit per service tier. 1 Transition Every state transition on every resource is recorded in resource_state_history: when it changed, what it changed from, what it changed to, and what triggered the change. ZopNight… 1 Triage When a cost anomaly fires, the first 15 minutes determine whether it becomes an incident (cost overrun, requires response) or stays an event (recorded, no action). The same… 1 Triage cadence The regular, typically weekly schedule on which recommendations are reviewed and sorted into apply, dismiss, or snooze decisions, preventing backlog accumulation. 1 Triage SLA If your team doesn't have a triage SLA today, set 15 minutes as the target. Adjust based on operational reality after the first month. 1 Trigger column The trigger column on the state-history timeline answers the operational question "who or what caused this transition?" Every transition carries one of five trigger types, with… 1 Trigger source Everything that changes a resource's state is recorded. The trigger source is recorded too (covered in L2). 1 Trust cloud vs trust ZopNight The two resolution paths for tag drift, where trust cloud treats cloud-side values as the corrected source of truth and trust ZopNight reverts unauthorized cloud changes back to… 2× Trust-but-verify Agents make up numbers when uncertain. The trust-but-verify discipline: 1 Two-source cost model The two-source cost model is the architectural pattern ZopNight uses for cost data, and the recommended pattern for any FinOps practice: maintain both a live calculated cost (rack… 1
Unattributed With tags, attribution flows from the resource. A shared RDS instance with team=identity,team=growth (multi-valued or with a shared-services convention) can be split by half. An… 1 Unattributed bucket Unattributed bucket at 18% of total spend. Best action: 1 Unattributed overlay The unattributed overlay is the visual companion to the Tag Coverage widget (M3.5.L4). Where the widget gives a percentage, the overlay shows where the percentage gap lives… 1 Unblended cost AWS CUR billing column; post-discount. 2× Unblended Cost label A cost-source label shown on report headers indicating that post-discount billing data is the active source, in contrast to the Rack Rate label which indicates costs calculated… 1 Unit economics Cost per business unit (MAU, order, request). 1 Unit economics dashboard A unit economics dashboard is the surface where the cost-per-X number becomes visible and discussable. The dashboard turns "we have a metric" into "the team sees it weekly." Five… 1 Unit metric This lesson covers the product mechanics: how to configure a unit metric, how to wire the source, how to read the overlay. The domain rationale for unit economics (why you want… 1 URL persistence The property that drill and filter state is encoded in the URL, making a view shareable (paste the link and a teammate sees the same state), bookmarkable, and reload-safe. 1 Usage-based attribution Equal split is the default for three reasons. Simplicity: no usage data required, no manual configuration. Predictability: teams know what to expect; the share does not change… 1 usePermission The ZopNight frontend uses a single hook, usePermission(), to decide whether to render an action. The hook reads the policy set encoded in the user's session token, checks against… 1 user_action error A remediation failure caused by a customer-fixable condition (missing permission, exceeded quota, resource in use, policy violation) that does not auto-retry and requires the… 1 Utilization The discount published on a commitment ("save up to 40%!") is the best case. The actual savings you realize depend on coverage and utilization. Most teams over-estimate their… 1
Validation A remediation's action step succeeds but validation fails. What happens: 1 Vanity metric A metric that measures activity rather than business impact (for example "reviewed 200 recommendations" or "spent 40K") with no denominator or outcome context, making it non-actionable. 1 Vanity metrics A cross-stage FinOps anti-pattern of tracking activity counts instead of outcomes, whose structural fix is switching KPIs from activity-based (reviews performed) to outcome-based… 1 Variable cost The cloud is variable cost. That is its defining property compared to on-prem. The FinOps practice should exploit elasticity: scale down at night, terminate when idle, use spot… 1 Variable validation Terraform default_tags + variable validation + CI script + cloud-native policy + auto-tagger = 96%+ coverage. 1 Variance analysis Notification routing per-threshold is configured in the budget itself. Different audiences get different alerts (covered in L3). Variance analysis at period-end is supported by… 1 Variance direction Whether a forecast miss was an over-forecast or an under-forecast, a distinction that matters because each has different business implications and calls for different calibration… 1 Variance review A period-end (typically quarterly) meeting that compares forecast against actual cost, quantifies the delta and accuracy, and analyzes drivers to feed the calibration loop for the… 1 Vault Every connected cloud account requires a credential: an IAM role, a service account, a service principal. ZopNight stores these credentials in a vault and uses them to call cloud… 1 Vendor lock-in The risk that leaving a share-of-savings vendor incurs high switching costs from knowledge transfer and setup overhead, mitigated by negotiating exit clauses (commonly a 90-day… 1 Verification checklist For team rollout: document the verification checklist in your wiki; ask each engineer to run it before relying on MCP for real work. 1 Viewer ZopNight ships with four system roles: Viewer, Editor, Admin, and SuperAdmin (default_roles.go), designed to cover the common 80% of role assignments without custom-role work.… 1 Visibility-driven accountability The mechanism where cost visibility alone (per-team dashboards shown to leadership) changes team behavior without formal chargeback, working when teams care about cost, leadership… 1 VPC endpoint S3 API calls from EC2 without a VPC endpoint: 1
Wake-for-job pattern A Databricks scheduling pattern where a cluster is configured to start just before a dependent job runs and stop afterward (for example waking 1:30 to 4 AM for a 2 AM nightly… 1 Walk stage The middle FinOps maturity stage of action without rhythm, where orgs run optimization sprints and achieve savings but watch those gains erode over 6 to 12 months for lack of a… 1 Warehouse sizing Selecting the right Databricks SQL Warehouse size (2X-Small to 4X-Large, roughly 1 to 256 nodes) based on concurrency and workload, which drives both cost factor and query… 1 Wasteful overrun A budget overrun driven by waste (forgotten resources, runaway processes, unauthorized spend) rather than legitimate growth, which warrants enforcement such as killing resources… 1 Webhook ZopNight notifications fire on schedule actions, override events, anomalies, and failures. Each notification can be routed to one or more channels. Channels are webhook-based:… 1 Weekend Scale-Down preset A preset schedule that stops resources for the weekend (midnight Saturday to Monday 8 AM) while running weekdays, yielding about 33.3 percent theoretical savings and suiting teams… 1 Well-architected framework The AWS Well-Architected Framework, a review methodology built on six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and… 1 Widget registry The widget registry is in code; each widget exports its required policy. The dashboard renderer reads the user's policy set and decides per widget. For new widgets, the policy… 1 Worker pool The bulk path uses a 4-worker pool to prevent burst load on the cloud provider's APIs. A bulk operation on 100 resources takes 3–5 minutes typically. 2× Workload Identity Federation Modern cred mechanism for GCP/Azure (no long-lived keys). 2× Workload schedulability Whether a Kubernetes workload can be scaled to zero or suspended for cost, where Deployments, StatefulSets, and CronJobs are schedulable but DaemonSets, ReplicaSets, Jobs, and… 1 Workload-level scheduling The workload-level scheduling preserves the cluster while saving cost on non-prod. 1 Write surface The UI is the highest-confidence write surface. The 30 seconds of "let me look" is worth it. 2× Write-with-approval Mental model: agent reads, human writes. Apply this when explaining to compliance, security, and skeptical engineering leaders. The read-only contract is durable; M6.6 covers… 2×
Year-over-year ZopNight's Reports → Unit Economics provides the canonical view with all five elements. The dashboard supports multiple unit metrics (primary + secondary) with toggles;… 1 Yellow state The early-warning traffic-light budget signal (75 to 100 percent of budget or off-pace projection) where spend is approaching budget but the outcome is undecided, requiring… 1
Z-score method A statistical anomaly detection method measuring how many standard deviations a cost value sits from the mean (z = (X - mean) / stddev), with severity tiers at z of 2 (warning), 3… 1 Zero-activity days A count of days in the lookback window (typically 30) with no operations on a resource, pulled from cloud activity logs, where a high count such as 22 of 30 signals a strong idle… 1 Zero-mutation guarantee The Adopt flow guarantee that ZopNight tracks and surfaces an existing cloud-side scaling configuration without ever modifying it, so cloud state remains exactly as it was and the… 1
·
No term matches that filter.