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 the normal CRUD API calls for user roles and permissions. Schema change is also handled with an API that enforces atomic updates. If errors exist, partial schema changes are not executed but rather the database restored to pre-schema change request.

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.

RogueDB utilizes cloud provider built-in AES-256 encryption for data at rest. All associated encryption keys are also managed and cycled routinely in accordance to cloud provider policies. In addition, no employees are granted access to the virtual machines hosting customer database instances. All deployments, updates, and modifications only occur through standardized CI/CD pipelines that undergo strict quality control review.

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. Any requests to bypass policy to access a client's database instance will be rejected. The only exception will be circumstances required by law.

3, 6, and 12 month subscriptions allow us to commit to committed use contracts and pass on cost savings to you. Our payment provider (Stripe) requires upfront payment when allowing customers to alter the subscription (eg. storage amounts).

Network usage gets billed after the end of each month (typically within 1-3 business days). This enables a consistent billing experience and monthly insights into network usage.

Subscriptions are not refundable. Modification to a lower compute tier subscription or reduce storage allocation occurs at subscription renewal. Modification to a higher tier compute plan or increased storage allocation occurs immediately with credit provided for the previous compute and storage.
‍
These policies are enacted to allow us to keep our prices competitive and accessible for all users. Otherwise, discounts for subscriptions could not be offered for compute and storage.

For write operations (create, update, and delete), each message counts as an operation. For read operations, index utilization contributes based on internal algorithms and each individual message evaluated for the query count as an operation.

While RogueDB has largely finalized internal mechanisms and accounting, we maintain the right to modify the internal mechanisms and accounting without notice. Updates are guaranteed to only occur with updated releases of the database to clients.

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/.

Please refer to gRPC's officual documentation for the languages currently supported: https://grpc.io/.

RogueDB has automated failback and failover mechanisms for outages in cloud services planned on the technical roadmap as a high priority item. In the meantime, we will be monitoring for outages with procedures in place to rapidly swap clients to working regions.

Any updates to RogueDB will always strive to be backwards compatible with notification ahead of time via email and social media platforms of planned downtime. However, we cannot always guarantee backwards compatibility despite our best intentions. In those cases, we will provide ample notification with solutions shared ahead of time to facilitate smooth transitions. RogueDB plans on only supporting one public version to streamline support and development.

For any events not covered by the above, RogueDB will communicate via email and social media platforms any relevant information.

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.