Navigate the console
Open an instance to work with one database. Use Summary for its status, Infrastructure for deployment details and Activity for events. The redesign is a local preview, so its sample values are not live operational data.
Screenshots show the current local console with sample data. They do not show live credentials or confirm a production change.
- Choose the organizationOpen the workspace that owns your database.
- Check the instanceUse Summary to confirm its identity and state.
- Open your taskChoose Data Explorer, Workbench or access settings.
- Review activityInspect the relevant result or event after an operation.
1. Pick an organization and instance
Select your organization, then open an instance from Instances. Check its name before running a query or changing a setting. Organization-level pages apply across the organization; instance pages apply to the selected database.
Check the connection state before acting. Local preview means the page is showing sample data or configuration drafts, not confirmed production state.
2. Find the right workspace
| Area | What it contains |
|---|---|
| Summary | Instance status and the next available action. |
| Infrastructure | Compute, storage and deployment details. |
| Activity | Instance events and progress. |
| Workbench | Query input, results and supported diagnostics. |
| Database login | Separate PostgreSQL credentials for the supported read-only connection. |
| Connect | API address, token instructions and PostgreSQL connection details. |
| Your tokens / Organization tokens | Tokens for the selected personal or organization scope. |
Controls that depend on an engine capability or a dedicated instance must be confirmed against that instance. A preview control is not a promise that a live change has been applied.
3. Browse your instances
The organization-level Instances page is the inventory. Open an instance to enter its workspace, or choose New instance to prepare a deployment. Organization team, usage, billing, and settings pages apply across that organization.
4. Explore data and connect an application
Data Explorer has four views: Data, Connections, Embeddings, and Indexes. Use namespace and table filters to narrow the scope. In Connections, switch between the schema map and record graph; Expand workspace gives the canvas more room without losing its controls.
Open Connect and choose API or PostgreSQL. For API access, copy the complete OC_URL and follow the token instructions shown for that instance. PostgreSQL uses a separate username and password. MCP setup is not exposed in the new connection panel while a compatible published server is being verified.
Review deployment and network settings under Infrastructure. The available actions depend on the instance; a visible preview is not confirmation that the engine supports or applied an action.
5. Review changes before applying them
A saved draft is different from an applied engine change. Read the resulting status, especially for network rules, feature switches, backup requests, and deployment settings. Deleting an instance or changing its credentials can affect connected applications; use the confirmation and impact details presented by the live console.
Next: explore a query
Open the Workbench guide for a first query, or create a table before loading your own data.