Pause and Resume for Cost Control

An Aura instanceA single Neo4j database running in Aura. bills for every hour it runs, including the hours nobody queries it. Nights, weekends, the three weeks between demo and follow-up. For production, that's the point. For development, testing, and training instances, those idle hours are the largest avoidable line on the bill.

Pausing is the lever. A paused instance stops its compute but keeps its storage, so your data, your configuration, and your connection URL all survive. On paid tiers, it bills at 20% of its standard rate, which covers the storage while the compute is switched off.