You can use the NeoSQL desktop app right away, without signing up or signing in. That is why two separate things decide what you can do: whether you are signed in, and whether the project you have open is a local project or an account project. Keeping the two apart explains why team features may be missing even though you are signed in, and why projects seem to disappear after you sign out.
Two separate things
| What it decides | |
|---|---|
| Signing in | Features tied to your account: the account tabs of My Page (subscription, workspace and so on), personal notifications, AI keys saved to your account, and whether you can see and create account projects. |
| Project type | Where the project is stored, and team features. Sharing and permissions, DDL approval, column masking, zero-knowledge encryption and the split between personal and team ERDs exist only in account projects. |
Put together, they look like this.
| Local project | Account project | |
|---|---|---|
| Desktop, not signed in | Create and open | Not shown |
| Desktop, signed in | Create and open | Create and open |
| Web app | Not available | Create and open (the web app always requires signing in) |
Signing in does not add team features to a local project. Team features are available only when you open an account project while signed in. How the databases the web app and the desktop app can reach differ is explained in Web and desktop.
Which projects each way of running can create
You create a new project with the menu. Which type it becomes depends on how you are using the app.
| How you run NeoSQL | Projects on the home screen | New projects |
|---|---|---|
| Desktop, not signed in | Local projects on this device | Always local projects. The dialog shows the notice You are not signed in — this project will be stored only on this device. Sign in to create account projects.. |
| Desktop, signed in | Local projects on this device and account projects. Local projects carry the Local label. | You choose in the Project Type field. The Account button is selected at first. |
| Web app | Account projects | Always account projects. |
- On a signed-in desktop, choose the type with the Account and Local buttons (1). A description of the chosen type (2) appears right below.
- To create an account project on a desktop that is not signed in, sign in first. How to sign in is explained in Sign-up and sign-in.
What is stored where
| Local project | Account project | |
|---|---|---|
| Project data (ERDs, table designs, SQL documents and so on) | Kept only in NeoSQL's storage on this device. There is no copy on the NeoSQL server. | Stored on the NeoSQL server. Each device that opens the project keeps a copy and syncs it with the server. |
| Database passwords | Kept separately in the operating system's secure storage. | Stored encrypted on the NeoSQL server. With zero-knowledge encryption on, they are encrypted on your device. |
| On another device | Cannot be opened. | Opens when you sign in with the same account. |
| With teammates | Not possible. | Invite them and work together. How many people a project can have depends on the plan (Plans and features). |
- A local project belongs to this device, not to a NeoSQL account. Signing in with a different account on the same device shows the same local projects.
- How passwords are encrypted, and what NeoSQL exchanges with its server even when you are not signed in, is explained in Security and where your data goes.
The type is fixed when you create a project
You choose the project type once, when you create the project, and you cannot change it later. A local project uses this device's storage and an account project uses storage that syncs with the server, so the place where data is kept is different. There is no way to turn a local project into an account project, or the other way round.
- To continue in the other type, create a new project of that type, add the connections again, and bring the tables of the real database into an ERD again (Document an existing database as an ERD). ERD layouts, notes and designs not yet applied to the database are not carried over.
- If you might work on the project with a team, sign in first and create it as an account project.
When you sign out or delete your account
You sign in from the user menu in the header, and sign out from the user menu or the menu. If there are unsaved changes, NeoSQL asks about them before signing you out.
| Event | Desktop | Web app |
|---|---|---|
| Sign Out | You return to the home screen for use without signing in. Local projects keep working, and the tabs of open local projects stay. The tabs of account projects close and open again when you sign in with the same account. | You go to the sign-in screen. |
| Sign-in expires | A notice appears. If you are looking at a local project, it stays; otherwise you go to the sign-in screen. Click the Continue without account link there to keep working without signing in. | A notice appears and you go to the sign-in screen. |
| Delete Account | Your account and your data on the server are deleted. Local projects are not on the server, so they remain on this device. | Your account and your data on the server are deleted. |
What is deleted with your account is explained in Deleting your account.
Device settings and account settings
Some settings are stored on the device rather than in your account. Settings stored on the device remain after you sign out and do not follow you to other devices.
| Setting | Stored on the device | Stored in your account |
|---|---|---|
| Language and time zone | Set in the Device Settings section of the screen while you are not signed in. | When you sign in, your account's settings take precedence. |
| Usage statistics | Set per device, whether or not you are signed in. | None. |
| AI provider keys | A key saved on the device in the desktop app is used only on that device, even without signing in. | A key saved to your account is used wherever you sign in, in the desktop app and the web app. |
When you open the My Page screen on a desktop that is not signed in, the tabs that need an account show a locked preview and ask you to sign in. How an AI key is chosen is explained in AI and MCP.
Features not available in local projects
The features below are used by several people through the server, so local projects do not have them, even when you are signed in.
| Feature | In a local project |
|---|---|
| Project sharing and members | There is no Collaborate button in the header. |
| Role permissions | There is no tab. |
| DDL approval | There is no button. |
| Column masking | There is no menu for marking sensitive columns. |
| Zero-knowledge encryption | There is no button or menu to turn it on. |
| Personal and team ERDs | Every ERD is shown with the Personal label. The Start Team Sharing & Collaboration... and Publish to Public... items appear with a lock and, when clicked, explain what they require. |
| ERD watermark text | There is no tab. |
ERDs, the SQL editor, code generation and dashboards work the same in local projects. The data dictionary works with official packs and dictionaries created on this device (Data dictionary), and AI works with a key saved on the device or in your account.
Things to keep in mind
- A local project exists only on this device. There is no copy on the NeoSQL server, so if you lose the device you lose the project too.
- On a computer that several people use, this device's local projects are visible whichever account is signed in. Create designs that others must not see as account projects.
- You cannot change the project type later. If you might work with a team, start with an account project.
Related pages
- Web and desktop: the differences in which databases each way of running can reach and which features it has.
- Sign-up and sign-in: how to sign in through the browser from the desktop app.
- Collaboration and permissions: how you work with teammates in an account project.
- Plans and features: the sharing limits and features that depend on the plan.
- New project: the dialog for creating a project.