MultiBase Studio
Get started with MultiBase Studio
Connect your first database, explore its objects and run a read-only query. This guide covers the desktop workflow; server permissions, SQL syntax and administrative operations depend on your database engine.
1. Install the desktop application
Choose the official package for your operating system on the download page. Check installer availability before starting. The Free plan supports up to three active connections without a credit card.
- Windows: use the 64-bit installer for Windows 10 or 11.
- macOS: choose the package for Apple Silicon or Intel that matches your Mac.
- Linux: choose AppImage or the Debian package for a compatible distribution.
2. Create and test a connection
Choose New connection, select the database engine and enter the connection details supplied by your database administrator. Test the connection before saving it. SQLite uses a local database file instead of a database server.
- For a local PostgreSQL installation, the host is often localhost and the default port is 5432. MySQL commonly uses port 3306. Use the values configured on your server.
- For remote databases, confirm network access, TLS certificates and any SSH tunnel requirements.
- Use an account with the permissions required for the task. A read-only account is a useful starting point for browsing data.
3. Run your first query
Open a query tab within the selected database. For PostgreSQL, MySQL or SQLite, SELECT 1; is a small read-only query that checks the SQL connection. Review the active connection and database before running any statement.
- Use Ctrl + Enter to execute a query and Ctrl + Space to request editor suggestions.
- Start with read-only queries and limit large result sets using the syntax supported by your engine.
- MongoDB and Redis use engine-specific commands; a SQL example is not a universal connection test.
4. Save queries and inspect results
Save reusable SQL scripts under the selected database with descriptive names. Use table, card or JSON views to inspect results. Keep read-only queries separate from scripts that change records or database structure.
- Check the current database before reusing a saved script.
- Review pending cell edits and the affected rows before applying changes.
- Export only the results and fields needed for your task.
5. Troubleshoot a failed connection
Read the connection error before changing settings. A timeout, authentication failure and missing database describe different problems and need different checks.
- Timeout or connection refused: check the host, port, database service, firewall and VPN or SSH tunnel.
- Authentication failed: verify the username, password and allowed authentication method without sharing credentials.
- Database or permission error: confirm the database name and ask its administrator to review access.
- TLS error: verify the configured certificates and server requirements.
6. Protect credentials and production data
Database connections run from your computer. Store credentials locally, review your server access policy and verify a usable backup before important changes. The privacy policy explains account and license data handling.
- Use a development or test database to learn editing and administrative workflows.
- When requesting support, include the operating system, application version, database engine and sanitized error message. Do not send passwords, tokens or sensitive records.