We’ve developed a set of tools that will allow you to run Neo4j Community in production, like backups, read-replicas, database metrics, query logs and more.
You can create a Snapshot of your database anytime or schedule automated Snapshots by choosing from our Snapshot Policies.
Snapshot Policies are flexible and prorated to the hour, can be disabled completely if not needed and offer scheduling options as frequent as every 3 hours and retention as long as 3 years.
Once the Snapshot is ready, it can be restored self-service from our Console into any database within your Organization or used to seed a new database.
Use our API to create a Disaster Recovery plan that suits your needs by automating Snapshot and Restore operations.
Read-replicas provide redundancy and increase data availability. Replicas are deployed automatically in different Availability Zones, providing a level of fault tolerance against zonal outages.
Additionally, if you add more than one replica, replication can provide increased read capacity as clients can send read operations to different servers.
If you enable query logs for your database, all your queries will be logged automatically. You will be able to search the query log and get all the information on past queries like execution time, client address, page cache hits, etc.
Apart from the server metrics, we have added a set of metrics that provide insights on how the database is performing. You can get information on transactions, queries, latencies, connections, etc.
Metrics can be additionally fetched via the public open metrics endpoint and used as a source for your own Prometheus or Datadog service.
Read-only users let you connect to the database with a user that only has read privileges.
This is especially useful for giving clients access with the peace of mind that no modification of your graph is possible.





