Native Windows installation
Use the native Windows installer when Docker is not available or is not permitted on the target host. The installer registers the API, web application, and Yjs collaboration service as Windows services. PostgreSQL can be installed locally by Setup or managed separately.
See Installation for shared prerequisites, endpoint defaults, backup guidance, and the Community security boundary.
Requirements
- A 64-bit Windows host supported by the release’s bundled dependencies.
- Administrator permissions during installation.
- Node.js 24 or newer for Advanced mode. Recommended mode can install the locked Node.js dependency when needed.
- An existing PostgreSQL database for Advanced mode, with a user allowed to apply the application’s database migrations. The bundled database is PostgreSQL 17; use the release prerequisites to check compatibility with other versions.
- No separate .NET runtime. The native API is self-contained.
The current native dependency lock targets Node.js 24.18.1 and PostgreSQL 17.10-2. Release packages may use newer versions.
Recommended installation
Recommended mode is intended for a clean workstation. If Setup detects an unrelated PostgreSQL installation, use Advanced and supply its connection details. Recommended mode can reuse an existing SES Modeler database when its saved configuration is available.
- Run the native Community Edition installer as an administrator.
- Select Recommended installation.
- On Application ports, keep the defaults (3000, 5150, and 1234) or enter other available ports. If a port is already in use, Setup suggests another available port. Review it and click Next again. Web, API, and Yjs must use different ports between 1024 and 65535.
- If PostgreSQL is not detected, choose Install PostgreSQL automatically to use the bundled PostgreSQL 17 installer.
- Review the configuration summary, then choose the installation directory or keep the default
C:\Program Files\SESModeler. - Keep Start SES Modeler services after installation selected to start the application. Choose the offered shortcuts and browser-opening task as needed, then complete Setup.
- Open the URL shown by Setup and verify the installation.
When the bundled PostgreSQL option is used, Setup installs PostgreSQL, creates the application database and user, writes the application configuration, registers the Windows services, and starts the services when that task is selected.
The installer can install Node.js 24 automatically when it is missing. It does not install a separate .NET runtime.
Configure manually later skips PostgreSQL setup. It does not produce a ready application: the API needs a configured database before it can pass readiness checks. Choose automatic installation for the complete Recommended path, or Advanced for a database you already manage.
Advanced installation
Use Advanced mode when PostgreSQL is already managed by your organization or is located on another host.
- Run the installer as an administrator.
- Select Advanced installation.
- On Application ports, keep the defaults or enter other available ports, as in Recommended mode.
- Enter the PostgreSQL host, port, database, username, and password. This path uses password authentication; leave the Windows integrated authentication (SSPI) option unchecked unless your database administrator has configured it for the API service’s Windows identity.
- Use the connection test if
psql.exeis available onPATH. A missing psql test tool does not install or configure PostgreSQL; the API readiness check after installation remains necessary. - Confirm that the database already exists and that its user can apply migrations. Ensure Node.js 24 or newer is installed before proceeding.
- Review the summary, choose the installation folder, select the service-start task, and complete Setup. Then verify the installation.
Advanced mode does not provision PostgreSQL. The database must already exist and be reachable from the machine running the API.
Verify the installation
The active installer registers these services:
SysMLv2-APISysMLv2-WebSysMLv2-Yjs
Check the services and the API readiness endpoint from PowerShell. The examples below use the default ports; substitute the ports selected during Setup when they differ:
Get-Service SysMLv2-API, SysMLv2-Web, SysMLv2-Yjs
Invoke-WebRequest http://localhost:5150/health/ready -UseBasicParsing
Start-Process http://localhost:3000The readiness endpoint is stronger than the liveness endpoint. It confirms that the API can reach PostgreSQL and that the standard libraries have loaded. On the first start, allow extra time for database migrations and standard-library initialization.
Native service logs are stored under:
C:\ProgramData\SESModeler\logsThe service error logs are SESModeler.Api.err.log, SESModeler.Web.err.log, and SESModeler.Yjs.err.log; their standard-output counterparts end in .out.log. The installer rotates service output logs at 10 MB. The application install directory normally contains the api, web, and yjs service payloads.
Optional LAN Trial
The native installer has an explicit LAN Trial option for demonstrations on a trusted private subnet. It is disabled by default.
LAN Trial:
- exposes the web, API, and Yjs services beyond loopback;
- uses unencrypted HTTP and WebSocket connections;
- uses shared Community access; and
- is not suitable for sensitive data, public networks, or a production server.
Keep the default Workstation profile unless the release instructions specifically call for a controlled trial. A secure shared deployment requires HTTPS/WSS, organizational identity, and explicit collaboration authorization; those pieces are not provided by the current Community deployment.
Backup and restore
Use pg_dump from your PostgreSQL installation or an appropriate PostgreSQL client package, or use an approved database administration tool. Target the host and database configured for SES Modeler.
Back up the database and model attachments before installing a new version. The default native attachment folder is C:\ProgramData\SESModeler\attachments. Keep copies of install-config.env, the API’s appsettings.json and appsettings.Production.json, and any release-specific configuration.
Updating
There is no transactional native update or automatic rollback flow.
- Back up the database, attachments, and configuration as described above.
- Run the new native installer as an administrator against the existing installation folder. Uninstalling first is not the normal upgrade step.
- Review the selected ports and network profile. Setup detects the existing installation, preserves its database connection and secrets, stops its services before replacing files, and registers the updated services.
- Keep the service-start task selected, then complete Setup.
- Verify
/health/readyon the selected API port and open the workspace.
The API applies EF Core migrations during startup. Do not install a new release without a current database backup.
Uninstalling
Uninstalling the native application stops and removes its Windows services and application files. An external PostgreSQL installation and its database are not removed.
If PostgreSQL was installed by Setup, the uninstaller offers a separate choice about removing that PostgreSQL instance. Removing it may remove its databases and data directory. Choose to keep it when the database contains models that must survive the application uninstall.
Troubleshooting
The API is not ready
Give the first start time to apply migrations and load standard libraries. Then inspect the API error log:
Get-Content "$env:ProgramData\SESModeler\logs\SESModeler.Api.err.log" -Tail 100Also confirm that PostgreSQL is running and that the configured database credentials are valid.
Node.js is missing
Recommended mode can install the locked Node.js dependency. In Advanced mode, install Node.js 24 or newer system-wide and run Setup again.
A port is already in use
The default ports are 3000, 5150, and 1234. If Setup reports that a port is already in use, review the suggested available port and click Next again. To change ports after installation, rerun Setup. Editing install-config.env alone does not update the running services.
The browser cannot connect to the API
Confirm that the API readiness endpoint responds on the selected API port and that all three services are running. On first start, refresh after the API has completed migrations and standard-library initialization. The web service receives the selected API and Yjs URLs at startup; you do not need to re-publish the web component after changing ports.
Next step
Once the application opens and the API is ready, build your first model. You can begin with an empty Model Repository.