# Fintech Cloud Cost: Nashville > How Financial Technology teams in Nashville cut non-production cloud waste with ZopNight, scheduled around Nashville working hours. Read-only, production excluded. Source: https://zop.dev/cloud-cost-optimization/nashville/fintech Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, geo, nashville, fintech --- A rapidly growing healthcare IT market with companies building EHR integrations and health data platforms. Nashville teams maintain HIPAA-compliant staging environments that are expensive to run and often left on 24/7 for compliance testing. For the Financial Technology teams among them, non-production waste follows a predictable shape: - Compliance requires full audit trails for all resource changes. - Sandbox and testing environments are expensive to maintain. - Strict separation between prod and non-prod. - Cost pressure from investors demanding efficient burn rate. Every one of those environments runs around the clock, the same as production while being used only during the working day (America/Chicago). ## Why Fintech teams in Nashville overpay The idle hours are the whole story. A dev, staging, QA, or demo environment left on overnight and across the weekend is billed at full price for compute nobody in Nashville is touching. Multiply that across the environments a fast-moving Fintech team keeps, and it becomes one of the largest controllable line items on the bill. ## How ZopNight helps ZopNight discovers every resource across AWS, GCP, and Azure, schedules the non-production ones to Nashville working hours, detects the idle stragglers, and reports what each cycle recovered against real usage. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), starts read-only, and excludes production by default. See it on [AWS EC2](https://zop.dev/zopnight/aws/ec2) and the discipline in [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 Nashville local time? Yes. Schedules run in your timezone, so resources stop and start around Nashville working hours automatically. ### Will this affect production? No. Production is excluded by default; only the non-production resources you choose are scheduled.