Your Vigthoria account controls database access across your builders, editor and CLI. Database plans are separate from hosting.
For Code 2.0.147, download the VigBase editor update. In Extensions, choose Install from VSIX, select the download, and reload the editor. This is a separate extension update; it is not installed automatically.
In Tools & Deploy, choose Connect database. Select an owned database. The Command Palette includes My Databases, Inspect Database Schema, Open Database SQL Editor, and Run Database SQL.
Run one SQL statement at a time. The editor shows the statement before execution.
vigthoria update vigthoria login vigthoria database list vigthoria database create my-app vigthoria database link DATABASE_ID vigthoria database schema vigthoria database query "SELECT 1"
Run these inside your project folder. Editor and CLI share .vigthoria/database.json. It contains the database ID, with no API key. Every request verifies the signed-in account’s access.
For bound values: vigthoria database query "SELECT * FROM tasks WHERE id = ?" --params '[1]'. Use --json for builder automation and --stdin for SQL read from standard input.
Create an application key in VigBase → Connect & API keys. Keep it in your server’s secret environment as VIGBASE_API_KEY. Your application must enforce permissions for its own users. Never put this key in a browser bundle.
Current Vigthoria hosting publishes static exports, including an index.html, from the current project files. Use vigthoria deploy preview --project ./dist for a built frontend. It does not execute Node.js servers or inject database credentials. Full application runtime deployment is not available yet.
Olena and ViAgen7 can access a connected database during development. Connecting a builder alone does not provision a production application server.