Document ID: M17-CERT-001-D4
Audience: First-time Jakten Risk customer (administrator or IT liaison)
Last updated: 2026-07-01
Status: Commercial Release 1
1. Purpose
This overview explains what you install, where it runs, and how jakten.net relates to your company data. Use it before choosing a deployment path.
2. Products and roles
| Component | What it is | Where it runs |
|---|---|---|
| Jakten Platform | Company shell — users, projects, licensing, product integration | Your Windows PC(s) or your office server |
| Jakten Risk | Paid analytical module — risk modeling and reporting | Same deployment as Platform (embedded or via server) |
| jakten.net | Jakten commercial services — checkout, licensing, email, documentation | Hosted by Jakten (not on your LAN) |
Jakten Risk requires Jakten Platform. Platform is included with your Risk subscription; you do not purchase Platform separately.
3. What runs where
On your network (customer-hosted)
| Data / software | Location |
|---|---|
| Project and risk data | Your PC or your office server |
| Documents and exports | Same deployment as databases |
| Desktop application | Each user's Windows workstation |
| Platform Server (office path only) | Office server or designated always-on Windows PC |
On jakten.net (Northland-operated)
| Service | Purpose | Customer project data? |
|---|---|---|
| checkout.jakten.net | Stripe purchase and activation key delivery | No |
| licensing.jakten.net | Subscription validation and activation redeem | No project data — subscription metadata only |
| docs.jakten.net | Customer guides and legal documents | No |
| [email protected] | Commercial support | No |
Important: jakten.net never stores your project or risk model data. Your analytical work stays on infrastructure you control.
4. Release 1 deployment profiles
| Profile | Best for | Summary |
|---|---|---|
| Single-user (GA) | One person on one PC | Install Platform on that PC; all components on that machine |
| Multi-user office (GA) | Two or more people on separate PCs | Platform Server on office server first; desktop clients on workstations |
| SQL Server (planned) | IT requires SQL Server operations | Not GA — documented as future release |
Use Choose Your Deployment to select the correct profile before installing.
5. Activation model
| Rule | Detail |
|---|---|
| One activation key per company deployment | Redeem once on the deployment that holds company data (single PC or office server) |
| Not per user | Coworkers do not activate individually on office deployments |
| Internet for activation only | Outbound HTTPS to licensing.jakten.net during activation; daily Risk work does not require internet |
6. Anti-pattern — separate silos
Do not have each coworker download Platform, run setup, and activate with the same key on separate PCs unless you intend separate single-user deployments (separate data silos).
For a team sharing one company, use the office deployment path: activate on the server deployment only.
7. Next steps
| Your situation | Read next |
|---|---|
| One user, one PC | Single-User Quick Start |
| Two or more users on separate PCs | Choose Your Deployment → Office Deployment Guide |
| Coworker (not administrator) | End-User Guide |
| IT firewall planning | Network and Firewall Requirements |
Related documentation
| Guide | Purpose |
|---|---|
| Choose Your Deployment | Decision tree |
| Deployment diagrams | Visual topology reference |
| Glossary | Platform, deployment, seat, entitlement terms |