Subscription · GritDB 1.1 Standard
GritDB subscription
You use GritDB on an annual subscription. The license, patches, new versions and technical support are included. Your servers and data stay on your side.
Price and billing unit
The price depends on the number of Units and the subscription term. VAT is not included. Datagrit works out the number of Units with you and sends you a quote.
1 Unit: 8 vCPUs · 64 GB of memory
For each server, divide the number of vCPUs set for GritDB by 8 and its memory (GB) by 64, and round each up. The larger of the two is that server's number of Units.
Show Unit examples and counting rulesHide Unit examples and counting rules
| vCPU | Memory | Units |
|---|---|---|
| 16 | 64 GB | 2 |
| 16 | 128 GB | 2 |
| 16 | 192 GB | 3 |
| 32 | 256 GB | 4 |
- What we count is the vCPU and memory limit set for GritDB, not momentary usage.
- Disk capacity is not counted.
- Standby and disaster recovery servers count if GritDB is installed on them and can be started. Keeping backup files does not count.
- One server can have up to 16 Units (128 vCPUs · 1,024 GB of memory). Beyond that, we agree on terms separately.
- Physical servers on your premises: We count the number of logical CPUs the OS sees (the nproc value) as vCPUs. On a server with hyper-threading turned on, this is twice the number of physical cores.
What the subscription includes
Included
- GritDB license (within the Units and term on the order form)
- Patches (bug fixes)
- License for new versions of the same edition released as generally available (GA) during the subscription term (we do not promise release dates)
- Standard technical support (09:00–18:00 on weekdays · Korea time)
- One remote support session for the first installation on a production server (if you bought from Datagrit)
- License for development and test servers (free of charge and not for commercial operation)
- Manual
Sold separately
- Premium support (severity 1 incidents 24/7 · one remote inspection a year · paid option)
- On-site work you hand over to Datagrit or a distributor or partner (installation, applying patches, upgrading to a new version)
- Regular inspections, training, query and design consulting, migration
- Server, cloud and storage costs
- CDC/ETL tools (when your operational database is not PostgreSQL)
Unlike buying a perpetual license and maintenance separately, the subscription includes the license for new versions.
Editions
The edition on sale now is Standard (GritDB 1.1). Enterprise is planned.
| Feature | StandardOn sale now · GritDB 1.1 | EnterprisePlanned |
|---|---|---|
| Dual engineThe transaction engine (PostgreSQL) and the analytics engine (GritDB engine) | Included | Included |
| Add as an analytics systemReceives changes from your operational database through PostgreSQL built-in replication, and also accepts writes from CDC/ETL tools that write to PostgreSQL (the tool is not included) | Included | Included |
| Analytics sessionThe analytics engine runs queries in analytics sessions (SELECT statements that read only registered tables) | Included | Included |
| ConnectionReporting and BI tools connect with PostgreSQL drivers | Included | Included |
| InstallationYour own servers (on-premises) · cloud virtual servers · networks without internet access | Included | Included |
| ManualQuickStart · Admin Guide · Troubleshooting | Included | Included |
| Features and support added in Enterprise | None | Announced at release |
The billing unit (Unit) is the same for both editions.
Installation options
Your own servers (on-premises)
GritDB installs on in-house servers you provide. It also installs on networks without internet access.
Your cloud account
GritDB installs on virtual servers you create in your cloud account (for example, Amazon EC2).
GritDB is not a cloud service run by Datagrit. For PoC, development, testing and production alike, you install it on in-house servers you provide or in your own cloud account. Your data also stays on your side. Datagrit does not rent out or run servers. It sells only the license, as an annual subscription.
Supported environments
| OS | Ubuntu 24.04 LTS |
|---|---|
| CPU | x86-64 · cx16 · sse4_2 instructions |
| Minimum specification | 16 vCPUs · 64 GB of memory (2 Units) |
| Disk | 200 GB + the size of the data you load |
| Open file limit | 65,536 or more |
| Source PostgreSQL | PostgreSQL 17 |
GritDB 1.1 does not encrypt connections (TLS), so use it inside the same private network as your operational database and applications. Other operating systems are not supported or warranted. New PostgreSQL major versions are supported after we finish testing them. Other major versions of the source PostgreSQL are checked in the discovery meeting. For other environments on your own servers, talk to us through Contact sales. Pre-installation checks are in QuickStart chapter 2 (in Korean).
Technical support
Datagrit provides technical support directly. If you bought from a distributor or partner, that company receives your requests first, and Datagrit takes over when needed. Wherever you bought your subscription, Datagrit provides patches and new versions.
Standard and premium support
| Item | Standard support | Premium support |
|---|---|---|
| Subscription | Included | Paid option |
| Support hours | 09:00–18:00 on weekdays (Korea time · excluding public holidays) | Severity 1 incidents: 24/7 · others: same as standard |
| Contact | Email support@datagrit.co · phone +82-70-7576-4947 (during support hours) | Standard support contacts and an emergency phone number for severity 1 incidents (given when you sign the contract) |
| First response to severity 1 incidents | Within 4 business hours | Within 4 hours (24/7) |
| Customer contacts who can request support | 3 per customer | 6 per customer |
| Regular inspection | None (paid option) | One remote inspection a year (report included) |
| Language | Korean | Korean |
Show severity levels and first responseHide severity levels and first response
| Level | Meaning | Standard support | Premium support |
|---|---|---|---|
| Severity 1 · Critical | GritDB on a production server has stopped or data corruption is suspected, and there is no workaround | Within 4 business hours | Within 4 hours (24/7) |
| Severity 2 · High | A function or performance problem affects your work, but there is a workaround | By the next business day | Within 4 business hours |
| Severity 3 · Normal | A problem with little effect on your work, questions about usage and settings, or feature requests | Within 2 business days | By the next business day |
- First response is the time until a Datagrit engineer first replies after receiving or taking over an incident. The time to resolve it depends on the cause, so we do not promise it.
- Severity 1 applies only to production servers. Business hours are 09:00–18:00 on weekdays (Korea time · excluding public holidays).
- If you bought from a distributor or partner, that company's response times and on-site support follow your contract with that company.
Show how remote support worksHide how remote support works
- Support is by email, phone and video call. You share your screen.
- Datagrit does not connect to your servers directly. We look together only over a connection you have approved in writing and opened yourself.
- You collect incident analysis data with the QuickStart 7.4 procedure, review it, and send it after masking anything you need to. Networks without internet access work the same way.
- Visits are not part of technical support. They are on-site work you hand over (charged separately).
Show what support does not coverHide what support does not cover
- Offered as paid services: writing, reviewing and tuning queries, data model design, migration, on-site work, regular inspections (on standard support), training
- Not supported: your applications, the source operational database itself, CDC/ETL/BI tools themselves (we do support the connection settings on the GritDB side), OS · hardware · network, installations outside the supported environments, installations you have modified, versions past EOS
- Servers smaller than the minimum specification are still covered by support. We look at performance problems after the server is raised to the minimum specification. With less than 8 GB of memory, the GritDB engine does not start.
- Problems where a specific query behaves differently than expected in GritDB are covered by support. If the cause turns out to be outside the scope, the remaining work can continue as a paid service.
Purchase steps
- 1
Discovery meeting
We look at a few slow reports with your DBA and check whether GritDB fits. We also set the scope, length and cost of the PoC.
- 2
PoC
We test with your data and reports. The PoC is paid. If you subscribe, we deduct the PoC fee from your first-year subscription fee. The evaluation license runs for up to 90 days, and an engineer certified by Datagrit works with you.
- 3
Units · quote
Datagrit works out the number of Units with you and sends you a quote.
- 4
Contract
You sign the order form and the license agreement.
- 5
Get the installation files
You receive the installation files and the checksum through separate channels and bring them onto your servers.
- 6
Installation · operation
You can install GritDB yourself with the QuickStart guide or have it installed for you (charged separately). Datagrit provides technical support directly. If you bought from a distributor or partner, that company receives your requests first, and Datagrit takes over when needed.
- 7
Renewal
You renew every year.
Datagrit handles quotes and contracts directly. You can also buy from a distributor or partner. In that case, that company sends you the quote. Start with Contact sales.
Show the quote preparation sheetHide the quote preparation sheet
If you need a budget quote first, fill in the fields below and email them to us at ask@datagrit.co. You only need to fill in what you know.
Download the Excel file: Korean · English
| Field | Choose | Write | See |
|---|---|---|---|
| 1. Company · contact person · contact details | — | Company · name · email · phone (optional) | Privacy policy |
| 2. Where you buy | Directly from Datagrit · distributor · partner | Name of the distributor or partner | Technical support |
| 3. Use | Add as an analytics system · Use as one database | — | Ways to adopt |
| 4. Source database | PostgreSQL · other database | PostgreSQL: version · location (your own servers · Amazon Aurora · Amazon RDS) · other databases: type · version · CDC/ETL tool | Supported environments |
| 5. Servers (each server where GritDB will run) | Purpose (production · standby · disaster recovery · development · test) | vCPU · memory · disk · OS · location · the Excel file calculates the Units | Unit counting rules · Supported environments |
| 6. Standby and disaster recovery | None · standby server · disaster recovery server | Number of servers (we agree on the method in the discovery meeting) | Unit counting rules |
| 7. Data · queries | — | Data size (now · in 1 year) · daily changes · 1 or 2 slow reports · concurrent users · TPS (roughly) | — |
| 8. Edition · support | Standard · standard support · premium support | — | Editions · Technical support |
| 9. Network | Connected to the internet · network without internet access | — | Installation options |
| 10. Schedule | — | When the budget is set · preferred start date · subscription term (in 1-year terms) | Term and expiry |
| 11. Other requests | — | Anything you want to add | — |
A budget quote based on this sheet is for reference only. It is not binding and is valid for 60 days. We send the formal quote after the PoC.
Term and expiry
- The subscription runs in 1-year terms, and you can buy as few as 1 Unit.
- We recommend 2 Units or more. The minimum specification in Supported environments(16 vCPUs · 64 GB of memory) is 2 Units. Smaller servers still get technical support, but we look at performance problems after the server is raised to the minimum specification. With less than 8 GB of memory, the GritDB engine does not start.
- Units you add during the term are added for the rest of the term. Reductions take effect at renewal.
- After the subscription ends, you can keep using all features for 30 days. After that, you can only query and back up (license agreement, Article 5). We do not delete your data.
- Renewal and termination terms are in the license agreement, which we give you when you sign the contract.
Version support period
Each version gets patches and incident analysis until EOL, and answers to questions and guidance on workarounds from EOL until EOS. After EOS, the version is no longer supported. Even if you start your subscription with 1.1, you move to the next GA version when it is released during your subscription. The new version license is included in the subscription, and the upgrade steps come with the new version's manual. We do not promise release dates.
| Version | EOL (end of patches) | EOS (end of support) |
|---|---|---|
| GritDB 1.1 | December 2026 | December 2027 |
- Until EOL, we provide patches as the latest patch release for that version.
- EOL and EOS for a new version are added to this table when it is released.
- New versions of the same edition released as GA during the subscription term can be used at no extra cost.
Frequently asked questions
Can we use GritDB if we already have a cloud data warehouse?
Yes. You can use both. A data warehouse collects data from many systems and analyzes long periods, while GritDB analyzes the data of your operational database right next to it. GritDB fits when operational data is hard to send outside the company, when reports need data before it reaches the data warehouse, or when report queries put load on the operational database. If your operational database is PostgreSQL, GritDB connects through built-in replication, so you do not need a separate ETL pipeline.
Do standby and disaster recovery servers need a subscription?
Every server where GritDB is installed and can be started counts. Keeping only backup files does not count.
How do you count cloud virtual servers?
We count the vCPUs and memory set for GritDB on the virtual server. For example, 16 vCPUs and 64 GB of memory count as 2 Units.
How do you count physical servers on our premises?
We count the number of logical CPUs the OS sees (the nproc value) as vCPUs. On a server with hyper-threading turned on, this is twice the number of physical cores.
Do we need to buy licenses for development and test servers too?
No. Subscribers get licenses for development and test servers free of charge. These licenses cannot be used for commercial operation. Like production servers, development and test servers are in-house servers you provide or servers in your own cloud account.
Does Datagrit provide the servers or cloud for the PoC?
No. The PoC also runs on in-house servers you provide or in your own cloud account. The PoC uses an evaluation license of up to 90 days, and an engineer certified by Datagrit works with you. If you adopt GritDB, the license comes as an annual subscription.
Is the PoC free?
Before the PoC, a discovery meeting checks whether GritDB fits and sets the scope, length and cost of the PoC. The PoC is paid. If you subscribe, we deduct the PoC fee from your first-year subscription fee. The deadline for the deduction is written in the PoC contract. You can ask for a discovery meeting through Contact sales.
What happens to our data when the subscription ends?
Under the license agreement, after 30 days you can only query and back up. We do not delete your data. The data stays in PostgreSQL tables inside GritDB, so you can take it out with PostgreSQL tools such as pg_dump.
Do we have to buy new versions separately?
New versions of the same edition released as GA during the subscription term cost nothing extra. We provide the upgrade steps in the new version's manual. If you get stuck upgrading yourself, technical support helps remotely. If you hand the upgrade over to Datagrit or a distributor or partner, the work is charged separately.
Can GritDB be installed on a network without internet access?
Yes. You install it from installation files and OS packages you bring in. You receive the checksum file through a different channel from the installation files. The steps are in QuickStart chapter 2 (in Korean).
What happens if we add servers during the term?
The added Units are added for the rest of the term. Reductions take effect at renewal.
Who supports us when an incident occurs?
If you bought from Datagrit, Datagrit receives your support requests. If you bought from a distributor or partner, that company receives them first, and Datagrit takes over remotely if needed. See Technical support.
Amazon Aurora, Amazon RDS and Amazon EC2 are trademarks of Amazon.com, Inc. or its affiliates.
Contact sales for a quote
Tell us the vCPUs and memory of your servers, and we will work out the number of Units with you and send you a quote.