On-premise edition
Your projects. Your infrastructure. Your control.
Every organisation has its own infrastructure, security and operating rules. Here is what running NUSK yourself involves today, so you can decide whether it fits before we talk.
Architecture and infrastructure
One application server and one database, inside your network or your own cloud account.
Application
A compiled NUSK server delivered as a container image from our private registry. It serves the web app and the API from one service.
Database
The setup wizard connects to PostgreSQL, MySQL, Microsoft SQL Server or Oracle. SQLite is available for small single-server installs. We confirm your database version during the assessment.
Files
Attachments and documents are stored on the server's disk or a mounted volume. Object storage such as S3 is not supported today.
Notifications, password resets and scheduled reports go through your own SMTP server.
AI (optional)
Connect your own provider: OpenAI, Anthropic, Azure OpenAI, Gemini, or a local OpenAI-compatible server such as Ollama, vLLM or LM Studio. With a local model, AI requests stay on your network. With AI switched off, nothing is sent anywhere.
Upgrades
New versions arrive as a new image. Database changes are applied automatically when the new version starts.
Security and identity
Built-in controls you can configure in Settings. Nothing here depends on the NUSK cloud.
- Single sign-on — SAML 2.0, plus Google and Microsoft sign-in (OpenID Connect).
- User provisioning — SCIM 2.0 from your identity provider.
- Multi-factor authentication — authenticator-app codes and recovery codes.
- Roles and permissions — per-module rights, project membership and read-only guest links.
- Sessions and passwords — password policy, session list and remote sign-out.
- Audit — an audit log in the app, which can also be streamed to your log or SIEM endpoint.
What connects to the internet
We would rather you hear this from us than find it in a firewall log.
- License check — activation and a daily check-in to nusk.dev. It sends the install ID, a machine fingerprint, the host name, the NUSK version and the number of active users. It never sends project data. Air-gapped sites can use an offline signed license file instead.
- Your AI provider — only if you turn AI on and choose a hosted provider.
- Integrations you enable — webhooks, Slack or Teams messages, GitHub links, Jira import and sign-in providers talk to the services you point them at.
- Email — through the SMTP server you configure.
Who does what
Installation is done together with your team. Support and upgrades are agreed for each deployment; there is no standard price list or published service level yet.
- You run — the server or cloud account, the database, backups of the database and documents volume, monitoring, TLS certificates and network access.
- We provide — the server image, help with installation and configuration, the license, and new versions.
- Built in — a health check endpoint for your monitoring, data export, and an in-app backup for the default SQLite setup.
- Not tested yet — multi-node high availability and automated disaster recovery. If you need these, we will assess them with you rather than promise them here.
- Licensing — a 15-day trial, then a license key for a number of users. Without a key the workspace becomes read-only; export and backup keep working.
How a deployment evaluation works
- You send your requirements using the form below.
- We review your infrastructure, identity and security needs together.
- We check feasibility — database, network, sign-in and any external services.
- We agree scope, responsibilities, commercial terms and next steps.
- We deploy only after you have approved the approach.
Request a deployment consultation
Tell us a little about your organisation. Whether NUSK fits depends on the technical assessment, so there is no commitment at this stage.
Prefer email? Write to nusk.dev@gmail.com.