Skip to content

Limitations

Nexaa’s Cloud Databases are built to be simple, reliable, and production-ready — but to ensure stability and maintainability, certain limitations apply. This page outlines the current constraints and support processes related to scaling, user management, and available plans.

Scaling and Resources

Cloud Databases come in predefined packages with fixed CPU, memory, and storage allocations. If your workloads require more capacity or if you're approaching your current resource limits:

  • Scaling CPU, memory, or storage must be requested via support.
  • We do not support automatic or user-initiated scaling at this time.
  • All resource adjustments require downtime and approval to maintain stability.

Storage Limits

Storage capacity is provisioned based on the package selected at database creation. If you need additional storage beyond your initial allocation:

  • Submit a support ticket to request a storage increase.
  • Scaling storage requires careful planning and maintenance window scheduling.

Shared vs Dedicated CPU

To support development and light workloads:

  • Shared CPU options are available for smaller, non-production packages only.
  • For production environments, all databases must use dedicated CPU to ensure consistent performance and isolation.
  • We reserve the right to deny shared CPU usage in workloads that show production-like behavior.

Additional Users

By default, each database is created with a single administrative user. If your application requires multiple database users:

  • You must submit a support request to add extra users.
  • We will create these additional users on your behalf and apply appropriate roles.

Connectivity Limitations

  • Database access is restricted to containers within the same Namespace.
  • External access to the database is not currently supported. If external connectivity is essential to your use case, please contact support to discuss possible workarounds or future roadmap alignment.

Package-Based Configuration

To keep operations predictable and secure:

  • All databases use predefined package templates with fixed specs.
  • You cannot arbitrarily change CPU, memory, or high availability settings after provisioning.