Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
26 commits
Select commit Hold shift + click to select a range
8af156b
Create get_started.md for FalkorDB Cloud DBaaS
danshalev7 Nov 17, 2025
d26effb
Update get_started.md
danshalev7 Nov 17, 2025
60e69c2
Rename get_started.md to index.md
danshalev7 Nov 17, 2025
aecc772
Create free-tier.md for Free Tier documentation
danshalev7 Nov 17, 2025
83c72de
Add metadata to cloud/index.md
danshalev7 Nov 17, 2025
3ee85e5
Update free-tier.md
danshalev7 Nov 17, 2025
f8789ca
Create features documentation for FalkorDB DBaaS
danshalev7 Nov 17, 2025
1d9c16e
Update Multi-Graph feature link in free-tier.md
danshalev7 Nov 17, 2025
ff5065d
Add pricing plans comparison for FalkorDB
danshalev7 Nov 20, 2025
122b842
Update cloud/index.md with images and links
danshalev7 Dec 1, 2025
1ca89d3
Revise features section and add demo link
danshalev7 Dec 1, 2025
ba3ba82
Revise video guide with image and sign-up link
danshalev7 Dec 1, 2025
c3548bd
Create Startup Tier documentation in markdown
danshalev7 Dec 1, 2025
d4056bb
Create Pro Tier documentation for FalkorDB
danshalev7 Dec 1, 2025
b1f9a34
Create documentation for FalkorDB Enterprise Tier
danshalev7 Dec 1, 2025
c40515b
Revise call-to-action and fix markdown tables
danshalev7 Dec 9, 2025
ebdc31c
Update pro-tier.md
danshalev7 Dec 10, 2025
72c35b1
Add billing and setup section to index.md
danshalev7 Dec 11, 2025
96dd6d5
Update headings and correct instance type labels
danshalev7 Dec 11, 2025
fb0fc67
Comment out clustered instances pricing section
danshalev7 Dec 11, 2025
b4cb17f
Change tutorial video thumbnail dimensions
danshalev7 Dec 14, 2025
f089ddd
Change thumbnail size in startup-tier.md
danshalev7 Dec 14, 2025
cbd2328
Modify Call-to-Action and image size in enterprise tier
danshalev7 Dec 14, 2025
c8b98db
Update cloud index with Free Tier and feature changes
danshalev7 Dec 18, 2025
60c754a
Revise features documentation by removing sections
danshalev7 Dec 18, 2025
d5abf45
Add 'Learn More' badge to cloud index
danshalev7 Dec 18, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions cloud/enterprise-tier.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
title: "Enterprise Tier"
parent: "Cloud DBaaS"
nav_order: 4
description: "FalkorDB DBaaS Enterprise Tier"
---
Comment on lines +1 to +6
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Resolve navigation order conflict.

Both cloud/enterprise-tier.md and cloud/features.md have nav_order: 4. This will cause unpredictable ordering in the documentation sidebar navigation. Adjust one of these files to use a different value. Based on typical tier hierarchies:

  • Free: 1
  • Startup: 2
  • Pro: 3
  • Enterprise: 4
  • Features: 5 (or place it elsewhere in the hierarchy)
🔎 Suggested fix for features.md front matter:
-nav_order: 4
+nav_order: 5

Committable suggestion skipped: line range outside the PR's diff.

🧰 Tools
🪛 GitHub Actions: spellcheck

[error] 1-1: Spelling check failed. Misspelled words detected by spellcheck: referenced in markdown content.

🤖 Prompt for AI Agents
In cloud/enterprise-tier.md (lines 1-6) and cloud/features.md, the front matter
uses the same nav_order: 4 causing sidebar ordering conflicts; change
cloud/features.md front matter to nav_order: 5 (or change one of the files to a
unique integer) so Enterprise remains 4 and Features becomes 5 to preserve the
intended tier hierarchy and eliminate the conflict.


![FalkorDB Cloud Enterprise Tier Banner](https://github.com/user-attachments/assets/f03bb001-1916-4e0f-9a82-cb8271309855)


# Enterprise Tier
FalkorDB's **Enterprise Tier** is designed for the most demanding workloads, offering ultimate performance, scale, and customization, with pricing determined on a **Custom** basis. This tier includes **every available enterprise feature**, such as **VPC Peering**, **Advanced Monitoring**, and **Dedicated Account Manager** support.

The Enterprise Tier is fully optimized for mission-critical applications, providing the highest levels of security, availability, and dedicated operational support. Deployment configurations are tailored to your specific infrastructure, scale, and compliance requirements.

## FalkorDB Pricing Plans Comparison

| Feature | FREE | STARTUP | PRO | ENTERPRISE |
| :--- | :---: | :---: | :---: | :---: |
| **Monthly Cost (from)** | **Free** | **$73** | **$350** | **Custom** |
| Multi-Graph / Multi-Tenancy | ✓ | ✓ | ✓ | **🟢** |
| Graph Access Control | ✓ | ✓ | ✓ | **🟢** |
| **TLS** | ✗ | ✓ | ✓ | **🟢** |
| **VPC** | ✗ | ✗ | ✗ | **🟢** |
| Cluster Deployment | ✗ | ✗ | ✓ | **🟢** |
| High Availability | ✗ | ✗ | ✓ | **🟢** |
| Multi-zone Deployment | ✗ | ✗ | ✓ | **🟢** |
| Scalability | ✗ | ✗ | ✓ | **🟢** |
| Continuous Persistence | ✗ | ✗ | ✓ | **🟢** |
| **Automated Backups** | ✗ | Every 12 Hours | Every 12 Hours | **Every Hour** |
| **Advanced Monitoring** | ✗ | ✗ | ✗ | **🟢** |
| **Support** | Community | Community | 24/7 | **Dedicated** |
| **Dedicated Account Manager** | ✗ | ✗ | ✗ | **🟢** |
| **Cloud Providers** | AWS, GCP, Azure | AWS, GCP, Azure | AWS, GCP, Azure | **AWS, GCP, Azure** |

## Terms
### Consultation and Pricing
> The Enterprise Tier is customized to your specific needs, leveraging dedicated resources, tailored support SLAs, and private deployment options. Pricing is calculated based on the custom configuration of cores, memory, and additional enterprise components.
>
> **For precise pricing, deployment details, and a dedicated consultation:**
> **[Contact our Sales Team](LINK_TO_SALES_CONTACT_HERE)**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

head -45 cloud/enterprise-tier.md | tail -10

Repository: FalkorDB/docs

Length of output: 547


Replace placeholder link with actual sales contact.

Line 41 contains a placeholder LINK_TO_SALES_CONTACT_HERE that must be replaced with a real email address. This will result in a broken link when the documentation is published.

🔎 Apply this diff to fix the link:
-> **[Contact our Sales Team](LINK_TO_SALES_CONTACT_HERE)**
+> **[Contact our Sales Team](mailto:info@falkordb.com)**
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
> **[Contact our Sales Team](LINK_TO_SALES_CONTACT_HERE)**
> **[Contact our Sales Team](mailto:info@falkordb.com)**
🤖 Prompt for AI Agents
In cloud/enterprise-tier.md around line 41, the contact link uses the
placeholder LINK_TO_SALES_CONTACT_HERE; replace that placeholder with the actual
sales contact (e.g., a proper mailto: sales@example.com or the canonical sales
page URL) so the link is valid and points to the real sales contact; ensure
formatting stays markdown link syntax and confirm the email/URL is correct
before committing.

>
> ⚠️ Prices are subject to change

## Getting Started

<a href="https://www.youtube.com/watch?v=fu_8CLFKYSs" target="_blank">
<img src="https://github.com/user-attachments/assets/d5519002-84ad-4076-9f64-150575d2eb7b" alt="FalkorDB Graph DBaaS Enterprise Tier Tutorial Video" width="640" height="360">
</a>

⚙️ To begin your Enterprise journey, schedule a consultation:
[![Contact Us](https://img.shields.io/badge/Contact%20Us-8A2BE2?style=for-the-badge)](mailto:info@falkordb.com)
67 changes: 67 additions & 0 deletions cloud/features.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
---
title: "Features"
parent: "Cloud DBaaS"
nav_order: 4
description: "FalkorDB DBaaS Features"
---

# Features

## Multi-Tenancy
Multi-tenancy lets you run multiple isolated graph databases within a single FalkorDB instance. Each tenant operates independently with its own data, queries, and access controls while sharing the underlying infrastructure.

Developers building SaaS applications need multi-tenancy to serve multiple customers without deploying separate database instances for each one. This approach reduces operational overhead and infrastructure costs while maintaining strict data isolation between tenants.

In practice, you create distinct graph databases for each customer or project, and FalkorDB handles the isolation automatically. Your application connects to the appropriate tenant database using different credentials or connection strings.

## Cloud Providers
### AWS
FalkorDB runs on Amazon Web Services infrastructure, giving you access to AWS's global network of data centers and integration with other AWS services. You can deploy FalkorDB instances in several AWS regions and connect them to your existing AWS resources.

Teams already using AWS benefit from keeping their graph database in the same cloud environment as their applications. This setup reduces latency and simplifies network configuration since your services communicate within the AWS network.

When you deploy on AWS, you choose your preferred region, and FalkorDB provisions the necessary compute and storage resources in that location.

### Google Cloud Platform (GCP)
FalkorDB integrates with Google Cloud Platform, allowing you to run graph databases on Google's infrastructure. You gain access to GCP's global network and can combine FalkorDB with other Google Cloud services.

Organizations using GCP for their applications should deploy FalkorDB in the same cloud to maintain consistent infrastructure management. Keeping your database and applications on GCP reduces cross-cloud data transfer costs and latency.

You select a GCP region during deployment, and FalkorDB sets up your graph database instance within Google's infrastructure.

> Note: Microsoft Azure is currently available in a Bring-Your-Own-Cloud configuration

## Storage
Storage defines how much disk space your graph database has for nodes, relationships, properties, and indexes. The amount of storage you need depends on your graph size and how much data you store in each node and relationship.

Applications with large knowledge graphs, social networks, or recommendation systems require substantial storage. Running out of storage stops your database from accepting new data, so you must monitor usage and scale accordingly.

FalkorDB allocates the specified storage capacity to your instance. You can track how much space your graph consumes and increase storage limits as your data grows.

## TLS
TLS (Transport Layer Security) encrypts all data transmitted between your application and FalkorDB. This encryption prevents anyone intercepting network traffic from reading your queries or results.

Applications handling sensitive data must use TLS to protect information in transit. Without encryption, credentials, personal data, and business logic become vulnerable when traveling across networks.

When you enable TLS, FalkorDB requires encrypted connections. Your application must configure its database client to use TLS, and all communication happens over secure channels.

## VPC
A Virtual Private Cloud (VPC) creates an isolated network environment where your FalkorDB instance runs separately from the public internet. Only resources within your VPC or those you explicitly authorize can reach your database.

Organizations with security requirements need VPC deployment to control network access to their databases. VPCs prevent unauthorized connection attempts and give you granular control over which services can communicate with FalkorDB.

You deploy FalkorDB into your existing VPC, and the database becomes accessible only through your private network. Your applications connect using private IP addresses instead of public endpoints.

## Persistence
Persistence ensures your graph data survives system restarts, crashes, or failures by writing changes to disk. Without persistence, you lose all data when the database stops.

Any application storing important data requires persistence to maintain durability. In-memory-only databases lose everything during unexpected shutdowns, making them unsuitable for production workloads.

FalkorDB persists data through regular snapshots and transaction logs. These mechanisms guarantee that committed transactions remain safe even if the system crashes immediately afterward.

#### Solution Architecture
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix heading level increment.

The "Solution Architecture" heading should be ### (h3) not #### (h4), as it follows the ## Persistence heading (h2). Heading levels should only increment by one level at a time per markdown lint rule MD001.

🔎 Apply this diff to fix the heading:
-#### Solution Architecture
+### Solution Architecture
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
#### Solution Architecture
### Solution Architecture
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

62-62: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)

🤖 Prompt for AI Agents
In cloud/features.md around line 62, the "Solution Architecture" heading is at
level h4 (####) but should be h3 (###) because it directly follows the h2
"Persistence"; change the heading from #### Solution Architecture to ###
Solution Architecture to ensure heading levels increment by only one level per
MD001.

Solution architecture support helps you design how FalkorDB integrates with your broader application infrastructure. This guidance covers connection patterns, data modeling approaches, and best practices for specific use cases.

Teams building complex systems benefit from architectural advice to avoid common pitfalls and optimize their graph database implementation. Poor architectural decisions early in development create technical debt that becomes expensive to fix later.

Architecture consultations provide recommendations on graph schema design, query optimization strategies, and integration patterns that match your application requirements.
45 changes: 45 additions & 0 deletions cloud/free-tier.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
title: "Free Tier"
parent: "Cloud DBaaS"
nav_order: 1
description: "FalkorDB DBaaS Free Tier"
---

![FalkorDB Cloud Free Tier Banner](https://github.com/user-attachments/assets/062cb5c5-d969-4481-ab1b-1802fea0732a)

# Free Tier
FalkorDB's free cloud tier gives you instant access to a graph database with multi-graph support and multi-tenancy capabilities. You can deploy on AWS or GCP with 100MB of storage and rely on community support to get started.

The free tier provides everything you need to explore FalkorDB and build initial prototypes. When your application grows and requires TLS security, VPC networking, high availability, automated backups, or dedicated support, you can upgrade to a paid plan that includes these enterprise features.

## FalkorDB Pricing Plans Comparison

| Feature | FREE | STARTUP | PRO | ENTERPRISE |
| :--- | :---: | :---: | :---: | :---: |
| **Monthly Cost (from)** | **Free** | **$73** | **$350** | **Custom** |
| Multi-Graph / Multi-Tenancy | **✓** | **✓** | **✓** | **✓** |
| Graph Access Control | **✓** | **✓** | **✓** | **✓** |
| TLS | ✗ | **✓** | **✓** | **✓** |
| VPC | ✗ | ✗ | ✗ | **✓** |
| Cluster Deployment | ✗ | ✗ | **✓** | **✓** |
| High Availability | ✗ | ✗ | **✓** | **✓** |
| Multi-zone Deployment | ✗ | ✗ | **✓** | **✓** |
| Scalability | ✗ | ✗ | **✓** | **✓** |
| Continuous Persistence | ✗ | ✗ | **✓** | **✓** |
| Automated Backups | ✗ | Every 12 Hours | Every 12 Hours | Every Hour |
| Advanced Monitoring | ✗ | ✗ | ✗ | **✓** |
| **Support** | Community | Community | 24/7 | Dedicated |
| Dedicated Account Manager | ✗ | ✗ | ✗ | **✓** |
| **Cloud Providers** | AWS, GCP, Azure | AWS, GCP, Azure | AWS, GCP, Azure | AWS, GCP, Azure |
| **Call-to-Action** | [Sign up](https://app.falkordb.cloud/signup) | [Sign up](https://app.falkordb.cloud/signup) | [Sign up](https://app.falkordb.cloud/signup) | [Contact Us](mailto:info@falkordb.com) |

#### Terms
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix heading level increment.

The "Terms" heading should be ### (h3) not #### (h4), as it follows standard heading hierarchy. Heading levels should only increment by one level at a time per markdown lint rule MD001.

🔎 Apply this diff to fix the heading:
-#### Terms
+### Terms
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
#### Terms
### Terms
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

36-36: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)

🤖 Prompt for AI Agents
In cloud/free-tier.md around line 36, the "Terms" heading is at level 4 (####)
but should be level 3 (###); change the heading from #### Terms to ### Terms so
the Markdown heading hierarchy increments by only one level and satisfies MD001.

> ⚠️ Free instances that aren't utilized for 1 day will be stopped, and deleted after 7 days.
Need an extension? Speak to [sales](https://www.falkordb.com/get-a-demo/))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix malformed Markdown link syntax.

Line 38 has an extra closing parenthesis after the link. The Markdown link should close properly with a single ).

🔎 Apply this diff to fix the syntax:
-Need an extension? Speak to [sales](https://www.falkordb.com/get-a-demo/))
+Need an extension? Speak to [sales](https://www.falkordb.com/get-a-demo/)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Need an extension? Speak to [sales](https://www.falkordb.com/get-a-demo/))
Need an extension? Speak to [sales](https://www.falkordb.com/get-a-demo/)
🤖 Prompt for AI Agents
In cloud/free-tier.md around line 38, the Markdown link contains an extra
closing parenthesis "https://www.falkordb.com/get-a-demo/))"; fix it by removing
the stray closing parenthesis so the link properly ends with a single ")" —
i.e., change the line to use a single closing parenthesis after the URL.


## Getting Started

[![FalkorDB Graph DBaaS Free Tier Tutorial Video](https://github.com/user-attachments/assets/56255f72-ff9d-4863-9942-b839257a723c)](https://www.youtube.com/watch?v=z0XO4pb2t5Y)

⚙️ Spin up your first FalkorDB Cloud instance:
[![Sign Up](https://img.shields.io/badge/Sign%20Up-8A2BE2?style=for-the-badge)](https://app.falkordb.cloud/signup)
63 changes: 63 additions & 0 deletions cloud/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: "Cloud DBaaS"
description: Cloud Offering
nav_order:
has_children: true
---

![FalkorDB Cloud Banner](https://github.com/user-attachments/assets/e436f01d-d60a-42cf-ac76-7e457180482e)

# FalkorDB Cloud DBaaS

Get started with FalkorDB's cloud offering. The platform provides several enterprise features, including multi-tenancy, across all tiers. Browse the available plans and select the one that suits your needs. You can scale and upgrade your deployment when ready.

## Features & Services

| Group | Features |
| :--- | :--- |
| **Availability & Resilience** | - High Availability<br>- Multi-zone Deployment<br>- Multi-Graph / Multi-Tenancy<br>- Automated Backups<br>- Continuous Persistence |
| **Security & Access** | - Graph Access Control<br>- TLS<br>- VPC Peering |
| **Deployment & Scaling** | - Dedicated Cluster Deployment<br>- Scalability |
| **Support & Monitoring** | - Dedicated Support<br>- Advanced Monitoring<br>- Dedicated Account Manager |
| ☁️ **Cloud Providers** | - AWS<br>- GCP<br>- Azure<br>- BYOC (AWS, GCP) |

[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](https://github.com/FalkorDB/docs/edit/Cloud-Docs/cloud/features.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Replace GitHub branch links with relative Markdown paths.

The "Learn More" and "Watch Demo" badge links reference the "Cloud-Docs" source branch (lines 24, 41, 48, 55, 62). After this PR merges to the main branch, these GitHub URLs will become stale or broken. Use relative Markdown paths (e.g., cloud/features.md instead of the full GitHub blob URL) for internal documentation links to maintain compatibility.

🔎 Example fix for line 24:
-[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](https://github.com/FalkorDB/docs/edit/Cloud-Docs/cloud/features.md)
+[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](./features.md)

Apply similar changes to lines 41, 48, 55, and 62, using ./free-tier.md, ./startup-tier.md, ./pro-tier.md, and ./enterprise-tier.md respectively.

Also applies to: 41-41, 48-48, 55-55, 62-62

🤖 Prompt for AI Agents
cloud/index.md around lines 24, 41, 48, 55 and 62: the badge links point to a
specific GitHub branch URL which will break after merge; replace those full
GitHub blob/branch URLs with relative markdown paths to the internal docs (e.g.,
change the line 24 link to ./cloud/features.md and similarly update lines 41,
48, 55, 62 to ./free-tier.md, ./startup-tier.md, ./pro-tier.md, and
./enterprise-tier.md respectively) so the links remain valid across branches and
in the main site.


---

### Billing & Setup
ℹ️ Prior to subscribing to any of FalkorDB's paid cloud tiers, please set up your billing information here:
> Adding your billing information is an easy, 3-step process:
> 1. Create a billing account ([Link](https://app.falkordb.cloud/billing))
> 2. Input your billing information [(Link)](https://billing.stripe.com/p/session/live_YWNjdF8xT3VGdlpBTEZxNUJKZk5kLF9UYUVZQ3A5WGpaZXp2Sk1CdVBTMUV5YWhqVUlXS3Vv01007QZVIlCR)
> 3. Create a new instance within your selected tier

![FDB-cloud-billing-how-to](https://github.com/user-attachments/assets/d5d6ce47-0bbc-4c71-b5fa-60a43677fb3f)

## Free Tier

The FalkorDB Free Tier provides a free FalkorDB instance for evaluation purposes. You can deploy, connect, and share the instance with minimal effort and no maintenance.

[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](https://github.com/FalkorDB/docs/blob/Cloud-Docs/cloud/free-tier.md)
[![Watch Demo](https://img.shields.io/badge/Watch%20Demo-black?style=for-the-badge)](https://www.youtube.com/watch?v=z0XO4pb2t5Y)

## Startup Tier

The FalkorDB Startup Tier provides a production-ready standalone FalkorDB deployment. Pick your machine size, add your dataset, and start extracting insights.

[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](https://github.com/FalkorDB/docs/blob/Cloud-Docs/cloud/startup-tier.md)
[![Watch Demo](https://img.shields.io/badge/Watch%20Demo-black?style=for-the-badge)](https://www.youtube.com/watch?v=xjpLPoQgo2s)

## Pro Tier

The Pro Tier provides a robust, dedicated environment to scale your application, including highly-available setups.

[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](https://github.com/FalkorDB/docs/blob/Cloud-Docs/cloud/pro-tier.md)
[![Watch Demo](https://img.shields.io/badge/Watch%20Demo-black?style=for-the-badge)](https://youtu.be/UIzrW9otvYM?si=P1too6QjZ5r9AHtB)

## Enterprise

The Enterprise Tier is fully optimized for mission-critical applications, providing the highest levels of security, availability, and dedicated operational support. Schedule a call with a FalkorDB solutions architect to learn more.

[![Learn More](https://img.shields.io/badge/Learn%20More-8A2BE2?style=for-the-badge)](https://github.com/FalkorDB/docs/blob/Cloud-Docs/cloud/enterprise-tier.md)
[![Watch Demo](https://img.shields.io/badge/Watch%20Demo-black?style=for-the-badge)](https://youtu.be/fu_8CLFKYSs?si=G7K6dN1i5tyqXTfC)
88 changes: 88 additions & 0 deletions cloud/pro-tier.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
---
title: "Pro Tier"
parent: "Cloud DBaaS"
nav_order: 3
description: "FalkorDB DBaaS Pro Tier"
---

![FalkorDB Cloud Pro Tier Banner](https://github.com/user-attachments/assets/2d39df96-f932-4cba-a124-bfff93f9a0ca)


# Pro Tier
FalkorDB's **Pro Tier** is your solution for high-performance, production-ready graph database workloads, starting at **$350/Month**. This tier is designed for applications requiring **High Availability (HA)**, **Multi-zone Deployment**, and robust **Scalability**. It includes essential infrastructure features like **Cluster Deployment** and **Continuous Persistence (AOF + Snapshot)**, backed by **24-hour Dedicated Support**.

The Pro Tier provides a robust environment to scale your application with confidence. When your needs extend to features like VPC Peering, Advanced Monitoring, or a Dedicated Account Manager, you can easily upgrade to the Enterprise plan.

## FalkorDB Pricing Plans Comparison

| Feature | FREE | STARTUP | PRO | ENTERPRISE |
| :--- | :---: | :---: | :---: | :---: |
| **Monthly Cost (from)** | **Free** | **$73** | **$350** | **Custom** |
| Multi-Graph / Multi-Tenancy | ✓ | ✓ | **🟢** | ✓ |
| Graph Access Control | ✓ | ✓ | **🟢** | ✓ |
| **TLS** | ✗ | ✓ | **🟢** | ✓ |
| VPC | ✗ | ✗ | **🔴** | ✓ |
| Cluster Deployment | ✗ | ✗ | **🟢** | ✓ |
| High Availability | ✗ | ✗ | **🟢** | ✓ |
| Multi-zone Deployment | ✗ | ✗ | **🟢** | ✓ |
| Scalability | ✗ | ✗ | **🟢** | ✓ |
| Continuous Persistence | ✗ | ✗ | **🟢** | ✓ |
| **Automated Backups** | ✗ | Every 12 Hours | **Every 12 Hours** | Every Hour |
| Advanced Monitoring | ✗ | ✗ | **🔴** | ✓ |
| **Support** | Community | Community | **24/7** | Dedicated |
| Dedicated Account Manager | ✗ | ✗ | **🔴** | ✓ |
| **Cloud Providers** | AWS, GCP, Azure | AWS, GCP, Azure | **AWS, GCP, Azure** | AWS, GCP, Azure |
| **Get started** | [Sign up](https://app.falkordb.cloud/signup) | [Sign up](https://app.falkordb.cloud/signup) | [Sign up](https://app.falkordb.cloud/signup) | [Contact Us](mailto:info@falkordb.com) |

## Terms
### Pricing Calculation
> We charge deployments based on **Core/Hour** and **Memory GB/Hour** usage. You pay **$0.200 per Core/Hour** and **$0.01 per Memory GB/Hour**.

## Standalone

| Instance Type | Monthly Cost |
| :--- | ---: |
| E2-standard-2 / m6i.large (Starting Instance) | $350.40 |
| E2-standard-4 / m6i.xlarge | $700.80 |
| E2-custom-4-8192 / c6i.xlarge | $642.40 |
| E2-custom-8-16384 / c6i.2xlarge | $1,284.80 |
| E2-custom-16-32768 / c6i.4xlarge | $2,569.60 |
| E2-custom-32-65536 / c6i.8xlarge | $5,139.20 |

## Replicated (High Availability, Master (x1), Replica (x1))


| Instances Type | Monthly Cost |
| :-------------------------------------------- | -----------: |
| E2-standard-2 / m6i.large (Starting Instance) | \$1,007.40 |
| E2-standard-4 / m6i.xlarge | \$1,708.20 |
| E2-custom-4-8192 / c6i.xlarge | \$1,591.40 |
| E2-custom-8-16384 / c6i.2xlarge | \$2,876.20 |
| E2-custom-16-32768 / c6i.4xlarge | \$5,445.80 |
| E2-custom-32-65536 / c6i.8xlarge | \$10,585.00 |


<!--
## Clustered (High Availability, Masters (x3), and Replicas (x3))

| Instances Type | Monthly Cost |
| :-------------------------------------------- | -----------: |
| E2-standard-2 / m6i.large (Starting Instance) | \$2,409.00 |
| E2-standard-4 / m6i.xlarge | \$4,511.40 |
| E2-custom-4-8192 / c6i.xlarge | \$4,161.00 |
| E2-custom-8-16384 / c6i.2xlarge | \$8,015.40 |
| E2-custom-16-32768 / c6i.4xlarge | \$15,724.20 |
| E2-custom-32-65536 / c6i.8xlarge | \$31,141.80 |
-->

> Use our **[graph size calculator](https://www.falkordb.com/graph-database-graph-size-calculator/)** to further estimate your cost.
> ⚠️ Prices are subject to change

## Getting Started

<a href="https://www.youtube.com/watch?v=UIzrW9otvYM" target="_blank">
<img src="https://github.com/user-attachments/assets/e19fdb04-e8fd-45c5-8361-97691ff3362a" alt="FalkorDB Graph DBaaS Pro Tier Tutorial Video" width="640" height="360">
</a>

⚙️ Spin up your first FalkorDB Cloud instance:
[![Sign Up](https://img.shields.io/badge/Sign%20Up-8A2BE2?style=for-the-badge)](https://app.falkordb.cloud/signup)
Loading
Loading