Installation & Launch
NeoSQL ships as a web app and as desktop apps for Windows and macOS. Pick the execution mode that fits your environment and follow the install / startup steps.
Which Execution Mode Fits You
NeoSQL ships in three execution modes. Pick the one that matches your environment.
Online (Web) — Fastest Way to Start
The quickest entry point: use NeoSQL directly in your browser with no install. After OAuth social login you can use the ERD canvas and SQL Editor immediately, and cloud sync enables real-time collaboration with teammates. The trade-off: you cannot reach internal-network or local DBs — only public databases that are directly reachable from the internet are supported.
Online (Desktop) — When You Need to Cross a Corporate Firewall
Choose the desktop app when your firewall only allows access from a developer's PC, or when the database lives behind a VPN. The desktop app connects to databases directly from your PC, so any database your PC can reach also works in NeoSQL, while cloud sync still keeps your team in lockstep.
Offline — For Air-Gapped Environments
Use offline mode in fully isolated networks where outbound internet is blocked by policy. Authentication uses a license key instead of OAuth, and all working data lives as JSON files inside the project's .neosql/ folder. Cloud sync, team collaboration, and AI features are unavailable; teams typically share the .neosql/ folder over Git to work together.
Using Online (Web)
How to start NeoSQL in a browser without installing anything.
Getting Started
Open the NeoSQL official site, sign in on the login page, and you'll land on the dashboard. Your active projects are listed; click "New Project" to create one or pick an existing project to continue. For full walkthroughs of sign-up, login, and project management, see the guides below.
Online (Desktop) Install & Start
The macOS and Windows desktop apps unlock internal/local DB connectivity as well as Offline mode. After install, the first launch flows through OAuth authentication to start using Online mode.
macOS Install (Apple Silicon)
How to install the NeoSQL desktop app on Apple Silicon Macs.
Download the DMG
Download NeoSQL-mac-arm64.dmg from the NeoSQL official site. Only Apple Silicon Macs are supported. Intel-based Macs are not currently supported.
Install the App
Open the DMG and drag the NeoSQL icon into the Applications folder.
Approve Gatekeeper
On first launch you may see an "unidentified developer" warning. Open System Settings → Privacy & Security and click "Open Anyway" next to NeoSQL. The warning won't appear again on subsequent launches.
Windows Install
How to install the NeoSQL desktop app on Windows. Microsoft SmartScreen may show a prompt at the download stage and again at the execution stage, so follow the steps below in order.
Download the Installer
Download NeoSQL-win-x64-Setup.exe from the NeoSQL official site.
Bypass Download SmartScreen (Microsoft Edge)
Microsoft SmartScreen may temporarily block newly-published, unsigned files at the download stage. When a block notice appears, follow the flow shown in the image below to retain the file. (Microsoft Edge enforces SmartScreen more strictly than other browsers.)

Bypass Execution SmartScreen (Windows)
Run the downloaded installer. When Windows SmartScreen shows the "Windows protected your PC" dialog, click "More info" → "Run anyway" to continue.
Finish Install & Allow Firewall
Follow the installer wizard; shortcuts will be created on your desktop and Start menu. No environment variables or separate Java install is required, and the neosql:// deep-link handler is registered automatically. On first launch, if Windows Firewall prompts about network access, choose "Allow access" so NeoSQL can reach your databases.
If installation is blocked in a corporate environment, ask IT to allowlist the NeoSQL installer. NeoSQL is preparing code-signing certification, after which these SmartScreen warnings will disappear.
Where Credentials Are Stored
The desktop app encrypts DB passwords and SSH keys in the OS-native secret store.
- macOS — Credentials are encrypted and stored in the macOS Keychain, scoped to the user account.
- Windows — Credentials are encrypted and stored in the Windows credential vault (DPAPI), scoped to the current user account.
Auto-Update
The desktop app checks for updates on launch and downloads them in the background. Once the download finishes, you'll see a prompt with "Restart Now" and "Later" options — choose "Later" to apply the update automatically the next time you quit the app. Auto-update does not run in air-gapped environments; IT must distribute new installer builds manually.
Getting Started
From the installed desktop app, click "Sign in via browser" — the default browser opens the NeoSQL login page, and once you authenticate, the neosql:// deep-link handler returns you to the desktop app automatically. From the dashboard you can create a new project or pick an existing one to start working. For full walkthroughs of sign-up, login, and project management, see the guides below.
Offline Mode NEW
How to authenticate with a license key and use NeoSQL in air-gapped environments. License issuance, renewal, and air-gapped deployment are covered in detail in the Offline License guide.
Prerequisite You must be on a plan that includes offline key issuance (Pro or above). The offline key menu is disabled on the Free and Basic plans. Issue a JSON key file from My Page first and transport it to the air-gapped PC.
Entering Offline Mode
Launch the desktop app and click the "Offline Login" link at the bottom of the login screen to move to the license key entry form.

Apply License & Authenticate
Drag-and-drop (or upload) the JSON key file — the license key and the three parameters below auto-fill. Check "Remember Me" to keep them for next launch, then click "Offline Authentication" — once validated, you'll move to the project selection screen. When the license expires, the session ends automatically; within 24 hours before expiry, the app shows a warning to remind you to renew. If you don't have a key file or need to renew, see the Offline License guide.
| Parameter | Description | Example |
|---|---|---|
JDBC_URL | JDBC connection URLs allowed in offline mode (multiple entries supported) | jdbc:mariadb://db.example.com:3306/mydb |
EXPIRED_DT | License expiration date (UTC) | 2026-12-31 23:59:59 |
LOGIN_ID | Offline user identification ID | user@company.com |

Air-Gapped Deployment
IT administrators can roll out NeoSQL to air-gapped fleets like this:
- On an internet-connected PC, download the desktop installer and the per-user license key files.
- Transport installers and key files to air-gapped PCs over an approved channel — USB, internal file server, etc.
- Each user installs the desktop app and registers their key file on the offline-mode entry screen.
- Repeat the same procedure whenever updates or key renewals are needed.
Offline Project Management
In Offline mode, projects live on the local file system. Create a new project under a chosen directory, or open an existing directory that already has a .neosql/ folder.
Create a New Project
Click the Create Button
Click the "New Database Project" button on the project management screen.
Pick a Directory
Click the "Search..." button in the Location field to choose a project directory.
Configure & Save
Enter the project name and DBMS, then click "Save". A .neosql/ folder is auto-created inside the chosen directory.

Open an Existing Project
Click Import
Click the "Import Project" button on the project management screen. (Shown only in offline mode.)
Pick the Project Directory
Choose a directory that already contains a .neosql/ folder. When project-config.json is detected, the project settings load automatically.
Data Storage Location
In Offline mode, all working data is stored as JSON files inside the project's .neosql/ folder. Sensitive credentials (DB passwords, SSH keys) live in the OS-native secret store (macOS Keychain / Windows DPAPI) and never end up inside .neosql/.
{project-root}/.neosql/
├── project-config.json # Project settings (name, DBMS, template pack)
├── connections/ # DB connection info
│ └── {connectionId}_{connectionName}/ # Per-connection directory
│ ├── connection.json # Connection settings (host, port, driver). Passwords excluded
│ └── {schemaName}/ # Per-schema directory
│ ├── {tableName}.json # Table definition (columns, indexes, FKs)
│ └── {tableName}_entity.json # Java Entity mapping info
├── erd/ # ERD diagrams
│ └── {erdId}.json # ERD definition (nodes, edges, layout)
└── sql/ # SQL Editor files
└── {sqlId}.json # SQL query body and result cacheNote: Sensitive credentials such as passwords and SSH keys live in the OS-native secret store (macOS Keychain / Windows DPAPI), not in the .neosql/ folder. You can safely commit .neosql/ to Git without leaking credentials.
Feature Differences by Mode
Compare available features across all three modes at a glance.
| Feature | Online (Web) | Online (Desktop) | Offline |
|---|---|---|---|
| Core | |||
| ERD Design / Edit | Yes | Yes | Yes |
| SQL Editor | Yes | Yes | Yes |
| Code Generation In Dev | Yes | Yes | Yes |
| Forward / Reverse Engineering | Yes | Yes | Yes |
| Database | |||
| Public DB | Yes | Yes | No |
| Private / Local DB | No | Yes | Yes |
| Collaboration | |||
| Team Collaboration (Real-time Sync) | Yes | Yes | No |
| Project Sharing / Invite | Yes | Yes | No |
| Cloud Backup | Yes | Yes | No |
| Extra | |||
| AI Features | Yes | Yes | No |
| Template Store (Download / Upload) | Yes | Yes | No |
Pick Online (Desktop) when you need to reach internal-network, local, or VPN/firewalled DBs; pick Offline when the environment blocks outbound internet.
Mode Switching Policy
Once you choose an execution mode, the data sync mechanism and storage location are locked in. There is no automatic switch — choose deliberately from the start.
Offline ↔ Online: No Direct Switch
Offline mode stores everything in a local .neosql/ folder, while Online modes (Web · Desktop) live in cloud storage — the storage layer itself differs. There is no cloud-side migration tool; switching modes means creating a new project and re-importing ERDs and table definitions manually.
Use Git to Collaborate in Offline Mode
Commit the .neosql/ folder to a Git repository to share ERDs, table definitions, and connection info across teammates even in Offline environments. Sensitive credentials such as passwords and SSH keys live in the OS-native secret store, so they're never part of the commit.
- Initialize a Git repository inside the offline project directory with git init.
- Commit and push .neosql/ to your internal Git server.
- Other teammates clone the repository and use "Import Project" in NeoSQL to load the folder.
- ERDs and table definitions look identical; each teammate configures their own credentials locally.
