Concepts

Plans and features

NeoSQL plans differ by features, not by how many things you can create. There is no limit on the number of projects, connections, schemas or tables in an ERD on any plan. What depends on the plan is how many people can work together and a few features. Check the pricing page for each plan's values and prices.

  • An account that is signed in but has no subscription is on the Free plan. When a subscription ends, the account returns to the Free plan.
  • If you use the desktop app without signing in, there is no plan. You use local projects only, and ERD images always carry the NeoSQL watermark (Sign-in and project types).
  • When you are signed in, the name of your current plan appears next to your user name in the header. You can see your subscription on the My pageSubscription screen.

What differs by plan

FeatureWhat depends on the plan
Sharing limitHow many people, including the owner, can be in one account project. On a plan with a limit of one, such as the Free plan, the Collaborate button does not appear in the header, so you cannot invite anyone.
Workspace seatsHow many people you can invite to create projects with your plan. Invitations waiting to be accepted also take a seat. On a plan without seats, such as the Free plan, you cannot use a workspace.
ERD image watermarkThe watermark added when you export an ERD as an image or copy it to the clipboard. Some plans fix the NeoSQL watermark, some have no watermark, some let you set the text in the Project settingsWatermark tab, and education plans fix a set text.
SQL result rows in the web appThe maximum number of rows you can receive and export as SQL results in the web app. Results beyond it stop at the limit. The desktop app has no such limit.
SQL history retentionHow long the SQL execution history of account projects is kept on the server. The history of local projects stays on this device for 7 days regardless of plan.

On a plan with a sharing limit of one there is no one to work with, so role permissions, DDL approval and real-time co-editing of team ERDs are used alone. How you work together is explained in Collaboration and permissions.

What is the same on every plan

FeatureOn every plan
Number of projects, connections, schemas and ERD tablesNo limit.
Code generationAvailable.
AI and MCPAvailable. AI uses the provider keys you register (AI and MCP).
Connection encryption and zero-knowledge encryptionAvailable. Zero-knowledge encryption is used only in account projects (Security and where your data goes).

Whose plan applies

An account project has one plan attached. It is not the plan of the person who created the project or the person who has it open, but the plan of the affiliation chosen when the project was created.

  • When you create an account project, choosing the My plan item in the Affiliation (Plan) field attaches your plan, and choosing a workspace you belong to attaches that workspace owner's plan. If you belong to no workspace, the field does not appear and your plan is attached.
  • Some features follow the project's plan and some follow the plan of the person using them.
FeaturePlan that applies
Sharing limitThe project's plan
SQL history retentionThe project's plan
ERD image watermarkThe project's plan (for a local project, the plan of the person exporting)
SQL result rows in the web appThe plan of the person running the SQL
Workspace seatsThe workspace owner's plan

Transferring ownership can change the project's plan.

  • When you transfer ownership of a project created with your plan, the project's plan changes to the new owner's plan. That is why the new owner's plan must be the same as or higher than the current owner's plan.
  • A project created under a workspace keeps following the workspace owner's plan when its ownership changes. Its ownership can be transferred only to the workspace owner or an active member of that workspace.
  • When a workspace owner deletes their account, projects owned by active members are not deleted; they move to those members' plans (Deleting your account).

When you move to a lower plan

When you move to a lower plan, or your subscription ends, and the sharing limit or workspace seats of the new plan are exceeded, NeoSQL does not delete the extra people. It disables them (workspace members are suspended). Projects and data remain, and people come back when you raise the plan again and enable them yourself.

What is exceededWhen it is cleaned upWhat cleanup doesWhere to restore
A project's sharing limitWhen the project owner enters the project, a dialog asks which members to keep. Until the owner finishes, other members cannot enter and see the Project Under Cleanup notice.Members not chosen are disabled and cannot enter the project. On a plan with a sharing limit of one, there is no choice: all shared members are disabled and the Project Sharing Disabled notice appears.The Enable button next to a disabled member in the Project Share Settings dialog
Workspace seatsWhen the workspace owner opens the home screen, a dialog asks which members to keep.Members not chosen are suspended and cannot create new workspace projects. Projects and data they already created stay as they are. On a plan without workspaces, all members are suspended.The Enable button on the My pageWorkspace screen
SQL history retentionNeoSQL does not ask.History older than the new retention period is deleted from the server.It cannot be restored.
  • In the dialog for choosing people, click the Apply Cleanup button to finish.
  • Disabled projects and connections are restored the same way: projects from the project context menu on the home screen, and connections from the Explorer context menuEnable menu.
  • When a plan change takes effect and how payment works is explained in Manage Subscription.

Things to keep in mind

  • Raising the plan again does not bring back disabled or suspended members by itself. Enable them yourself. Enabling also works only within the sharing limit and seats of the new plan.
  • The sharing limit follows the project's plan. Upgrading a teammate's plan does not raise the sharing limit of a project they joined as a member.
  • Projects created by workspace members follow the workspace owner's plan. When the owner moves to a lower plan, the sharing limit of those projects goes down too.