Deployment Diagrams

Document ID: M17-CERT-001-D11

Audience: Customer administrator and IT liaison

Last updated: 2026-07-01

Status: Commercial Release 1

Visual reference for Release 1 deployment profiles. See Deployment Overview for narrative explanation.

1. Commercial ecosystem

jakten.net services

checkout.jakten.net
licensing.jakten.net
docs.jakten.net
Commercial email
Does not store customer project data

Your network (customer infrastructure)

Profile 1 — Single-user

One Windows PC
Platform + Risk on same machine
Embedded Platform Server

Profile 2 — Multi-user office

Platform Server on office server
Shared company databases
Desktop clients on workstations (LAN)

Commercial ecosystem. Jakten.net handles checkout, licensing, documentation, and email only. Your project and risk data remain on PCs or servers you control. Activation uses HTTPS once; routine work stays on your network.

2. Single-user profile (Profile 1)

Windows PC

Jakten Platform desktop
Platform workspace
Jakten Risk workspace
Embedded Platform Server (single-user company data)

licensing.jakten.net

Single-user profile. All Platform and Risk components run on one Windows PC. Activate once on that PC. No separate server is required.

Activation: Once on this PC.

3. Multi-user office profile (Profile 2)

Office server

Platform Server (Windows Service)
Shared company databases and documents
Activate subscription once here

licensing.jakten.net

Workstation A

Jakten Platform desktop
Connect and sign in

Workstation B

Jakten Platform desktop
Connect and sign in

Multi-user office profile. The administrator activates once on the office server. Each workstation installs the desktop client, connects to the server URL, and signs in with company credentials.

Activation: Once on server only. Workstations connect and sign in.

4. Licensing vs installs

Purchase: 5 Risk seats for Acme Construction

One company deployment

One office server (shared data)
One activation redeem on the server

Five named users

Five seat assignments in Administration
Five desktop installs connecting to the same server

Not this: five separate activations on five isolated PCs — that creates five separate company data silos.

Licensing versus installs. Seat count licenses people, not separate company deployments. One office server holds shared company data; each licensed user gets a desktop install that connects to that server.

See Choose Your Deployment anti-pattern guidance.

5. Anti-pattern — multiple siloed installs

Wrong for a team sharing one company

PC-1 Silo A

PC-2 Silo B

PC-3 Silo C

Right for a team