Infrastructure & Data
Controlled acceptancePostgreSQL.
Governed by your Organization.
Managed Databases is undergoing controlled integration acceptance. Public provisioning and customer billing are not enabled. Availability requires a separate release decision.
Organization-owned tenancy. Built on verified Qwibik Cloud access controls.
Direct PostgreSQL
TLS required
Account verification
Separate reveal and rotation permissions
Public creation disabled
Release approval required
Live acceptance is pending
One explicitly authorized disposable database must complete provisioning, secure connection, rotation, usage inspection and verified deletion. This illustration contains no customer resources or credentials.
Pooling, automated customer backups, branching and point-in-time restore controls are not exposed by this service.
Engineered for production
Purposeful capabilities. Built for modern architecture.
Organization-owned resources
Database identity, access and lifecycle belong to your Organization. Viewing metadata does not grant access to credentials.
Direct PostgreSQL connections
The Connect view supplies provider-observed direct connection details. TLS is required. Pooled endpoints are not currently exposed by Qwibik.
Verified credential access
Credential reveal and password rotation use separate permissions and Qwibik Account verification. Passwords stay in protected server-side storage.
Durable lifecycle operations
Create, rotate and delete requests retain operation history. Uncertain provider outcomes require reconciliation before another destructive attempt.
Measured provider usage
Usage preserves provider units and reporting periods. Delayed or unavailable measurements are identified. Provider observations are not finalized customer charges.
Explicit recovery boundaries
Export and restore procedures are documented. Qwibik backup, branching and point-in-time restore controls are not available; no recovery or retention SLA is offered.
Controlled acceptance
A verified path before customer availability.
A separately authorized, disposable acceptance must verify the complete lifecycle before a customer release is considered.
Approve the scope
Agree on the Organization, provider account, region, PostgreSQL version, compute, budget, test window and cleanup owner. Public provisioning stays disabled.
Verify the connection
After authorized provisioning, retrieve credentials with Account verification and establish a certificate-verifying TLS connection.
Verify password rotation
Confirm new credentials work and previous credentials are rejected. Resolve uncertain outcomes through the existing operation history.
Measure and clean up
Inspect actual provider reporting, delete the disposable database and verify provider removal and credential erasure.
Technical specifications
Current service boundaries
Frequently asked questions
Essential details for your team.
Can I create a database today?
General customer provisioning is disabled. One disposable integration acceptance requires explicit authorization and approved Organization scope before any project is created.
Are pooled connections available?
The current Connect experience exposes direct PostgreSQL connection details only. Follow the actual host and port supplied for your resource; no separate pooled port is promised.
Does this change Qwibik One storage?
No. Qwibik One retains its separately governed internal persistence. Customer Managed Databases do not provision a database per Workspace or introduce a One storage integration.
What backup and restore guarantees are offered?
Qwibik has not released automated customer backup, branching or PITR controls, or approved recovery windows and retention SLAs. Export and restore verification remain explicit procedures.
Plan your database requirements.
Discuss availability and operating requirements. Public activation will follow a separate approved release.