PRODUCT GUIDE / PRODUKTLEITFADEN
VigBase Databases
VigBase is Coder’s project database workspace. Create a SQLite database, design tables, inspect rows, run bounded SQL and connect a supported application through scoped API access. Keep database identity with the project and store secret keys in the appropriate server configuration.
Your first workflow
- 01
Create or select your database.
- 02
Define tables and test queries on suitable sample data.
- 03
Create the least scope needed for the application.
- 04
Connect from the supported backend and keep a backup.
Available working areas
Tables and row data
Create the schema and manage the data in your selected database.
SQL workspace
Run a supported statement with bound parameters and inspect bounded results.
Scoped application access
Use the offered read, write or builder key scope and revoke access when it is no longer needed.
Backups and usage
Download supported backups and inspect the database’s usage view.
Check the actual result
SQLite tables, query results, scoped access and downloadable backups.
Review the output against your task before sharing, publishing or relying on it. Retain the project files or records needed to continue.
Access and product scope
Database ownership, quotas and key scopes control access. Application backends must enforce their own end-user permissions.
VigBase provides SQLite and supported REST access. Authentication, realtime subscriptions and object storage are separate services; static hosting does not execute a database backend.
If the next step does not work
I reach sign-in or access is denied.
Sign in with the intended Vigthoria account and reopen this product. Check the selected project, owner or team role and the current product entitlement in User Hub.
The task is queued or a required feature is unavailable.
Inspect the actual job and service state. Check whether the chosen route needs a provider connection, device support, signing setup or an enabled account feature. Keep a saved copy before retrying a completed action.
I need product support.
Include the product, action, time, visible error and relevant job or project identifier. Use a minimal example and keep passwords, secret keys and confidential source material out of the public form.