# FinOps Automation: Nairobi > FinOps Automation for Nairobi teams with ZopNight, scheduled around local working hours. Read-only setup, production excluded by default. Source: https://zop.dev/cloud-cost-optimization/nairobi/finops Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, geo, nairobi, finops --- East Africa's Silicon Savannah, with mobile-first fintech and agritech companies driving cloud adoption. Nairobi teams run non-production environments in eu-west-1 and af-south-1, often with M-Pesa integration testing environments that are costly when idle. Bridge the gap between engineering and finance with automated cost tracking, team budgets, savings reports, and provider-level breakdowns across AWS, GCP, and Azure. For Nairobi teams the lever is local: non-production runs around the clock, but the people who use it only work the Africa/Nairobi day. ## The Nairobi angle Every hour outside Nairobi working hours is billed at full price for compute no one is touching. FinOps Automation is about closing exactly that gap, and because ZopNight schedules in your timezone, the resources follow your team's actual day rather than a server's clock. ## How ZopNight helps Discover across AWS, GCP, and Azure, schedule non-production to Nairobi hours, detect idle, and report what each cycle recovered against real usage. 490 built-in audit rules across AWS (216), GCP (127), and Azure (147); setup is read-only and production is excluded by default. See [AWS EC2](https://zop.dev/zopnight/aws/ec2) and [FinOps](https://zop.dev/learn/finops). ## How ZopNight schedules non-production resources The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every non-production resources across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled. Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like "dev-cluster" or "staging-db" so a whole environment follows one cadence. Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a non-production resources ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it. ## Getting started Getting started is intentionally low-stakes: - Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage. - Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status. - Create a schedule in your timezone and attach the non-production resources or groups you want it to cover. - Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing. Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action. ## Frequently asked questions ### Does scheduling use Nairobi local time? Yes. Schedules run in your timezone, around Nairobi working hours.