Plans and Placements

Understanding the feature sets and datacenter availabilities of the different tiers

GrapheneDB offers a wide spectrum of plans for different data set sizes and workloads. Choosing the right plan will depend on your dataset and data model, complexity of queries, and throughput expectations.

For detailed information, features and prices of our different our tiers and plans, please refer to our pricing page.

Plans and tiers

All of our plans are hosted on Amazon Web Services dedicated instances.

Single tier

For dedicated stand-alone deployments, select one of our Single plans. Plans have been designed to ensure enough resources for each dataset size.

You can easily scale up or down your deployment using our change plan feature. Your connection settings and authentication credentials will be the same after this operation. You can read more on changing plans [here]](doc:database-plan-upgradesdowngrades).

Cluster tier

For causal clustering deployments, select one of our Cluster plans. Plans have been designed to ensure enough resources for each dataset size.

Same as on a single tier, you can scale your dataset when it’s needed with our change plan feature. Your connection settings and authentication credentials will be the same after this operation and no downtime is involved in the operation.

Deployment options

GrapheneDB offers the following deployment options in the different tiers:

Neo4j Community

Neo4j Enterprise (BYOL)

ONgDB

Single

Yes

Yes (on demand)*

Yes (on demand)*

Cluster

No

Yes

Yes

  • Reach out to support if you want to deploy a single dedicated database running Neo4j Enterprise (BYOL) or OnGDB.

Legacy plans

All plans that were deployed before September 2020 are marked as legacy and scheduled for migration.

You will see the migration date in a banner in the Overview view page in the coming days, and also a button to op-in for the migration.

Legacy versions

Additionally, all plans that are running Neo4j 3.1 or below will need to upgrade the Neo4j version to be able to use new plans and opt-in for the migration.

If that’s your case you can use the Upgrade Neo4j feature that you will find under the Admin tab.

Storage Limit Enforcement

Database storage is limited by disk size. GrapheneDB sends the following automated notifications to inform the user when the database is close to its storage limit:

  1. A warning email is sent to the account owner when a database reaches 70% of the storage limit
  2. A final notification is sent to the account owner when a database reaches 100% of its storage limit. At this point, the database is set to read-only mode

Information on how to deal with databases that have exceeded their limits and have been switched to read-only can be found here.

Placements

To ensure maximum performance, databases should be hosted as close as possible to the application. GrapheneDB offers hosting in most AWS regions while creating the Private Network that will ensure that your database is always secured deployment inside an AWS VPC.

GrapheneDB supports almost all AWS regions. If you don’t find a region below please reach out to support and you will get information on the status of supporting it:

Region name

Region code

US East (N. Virginia)

us-east-1

US East (Ohio)

us-east-2

US West (N. California)

us-west-1

US West (Oregon)

us-west-2

Canada (Central)

ca-central-1

EU (Ireland)

eu-west-1

EU (London)

eu-west-2

EU (Paris)

eu-west-3

EU (Frankfurt)

eu-central-1

EU (Stockholm)

eu-noth-1

Asia Pacific (Tokyo)

ap-northeast-1

Asia Pacific (Seoul)

ap-northeast-2

Asia Pacific (Singapore)

ap-southeast-1

Asia Pacific (Sydney)

ap-southeast-2

Asia Pacific (Mumbai)

ap-south-1

Updated about a month ago

Plans and Placements


Understanding the feature sets and datacenter availabilities of the different tiers

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.