RogueDB uses native programming language APIs to directly integrate with development efforts just like any other built-in data structure (lists, dictionaries, maps, vectors, etc.). This eliminates the need for structured querying languages and enables a very low barrier of entry for all developers.

Advertised performance is achieved out of the box without the typical extensive configuration required for other databases. All data operations are analyzed automatically to enable optimal performance every time.
‍
Database management is leveraged through API calls for user roles and permissions. Programmatically define and utilize the same procedures with code as infrastructure. The ability to codify allows for integration in preferred programming languages with seamless integration into version control systems, code ownership systems, and CI/CD pipelines.*

*Will be supported in future releases.

All connections with RogueDB databases use SSL/TLS paired with token based authentication. Any attempts to access a database with an unencrypted channel or a verified token are rejected. OAuth will be supported in future releases as an alternative authentication mechanism.

In addition, RogueDB works with cloud platform providers to ensure data at rest remains encrypted and secure. The only time we interact with a customer's database are for deployment, data transfers, and decommission of databases (eg. cancel or modification of subscription) through automated CI/CD pipelines. No employees have direct access to the underlying cloud infrastructure. All interactions occur through CI/CD pipelines with rigorous access and quality controls.

RogueDB will not retrieve, access, modify, or store data on behalf of the customer outside the services provided in a subscription plan under any circumstances, except as required by law.

Please refer to our Privacy Notice (link at the bottom of the website). This takes only a few minutes to read.

Please refer to our Terms of Service (link at the bottom of the website). This takes only a few minutes to read.

Discounts for short, mid, and long-term commitments at 3, 6, and 12 months respectively are 5%, 10%, and 15% respectively. Long-term commitment discounts are contingent on no modification to a dedicated plan's compute tier and a shared plan's compute tier not dropping to a lower tier. Shared plans offer the option to purchase expected storage use upfront for a 50% discount.

Network and storage usage (eg. not pre-paid shared plan storage) are invoiced at the end of each month.

Please refer to the Terms of Service for the cancellation and modification policies. These policies are enacted to allow us to keep our prices competitive and accessible for all users.

For write operations (create, update, and delete), each message is counted a 1 operation. For read operations, the log2 of messages of loaded chunks plus the messages returned per sub-query in a search operation.

Example
Stored Data (Single Chunk): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Search Criteria: data < 3 OR data >= 9
Operations: 2 + 2 (data >= 9) + 8 (ceiling(log2(10)) * 2)
Total Operations: 12
Explanation: data < 3 returns 2 messages. data >= 9 returns 2 messages. The entire chunk is searched twice due to two sub-queries.

The methodology results in a net reduction for operations counted against throughput limits. Calculations are biased towards favoring customers with a reasonable approximation of true operation counts required to retrieve and write data, independent of implementation details.

Official support includes the official support for Protocol Buffers. This includes C++, Java, Go, Ruby, C#, and Python. Additional unofficial support for Protocol Buffers are for the following languages: C, Haskell, Perl, Rust, and others.

Please refer to the Protocol Buffers official documentation for more details: https://protobuf.dev/reference/other/.