Jakten

Deployment Overview

Document ID: M17-CERT-001-D4

Document ID: M17-CERT-001-D4

Audience: First-time Jakten customer (administrator or IT liaison)

Last updated: 2026-10-16

Applies to: Jakten Platform 2.0


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

ComponentWhat it isWhere it runs
Jakten PlatformCompany shell — users, projects, licensing, product integrationYour Windows PC(s) or your office server
Jakten RiskPaid analytical module — risk modeling and reportingSame deployment as Platform (embedded or via server)
jakten.netJakten commercial services — checkout, licensing, email, documentationHosted by Jakten (not on your LAN)

Jakten Risk and Jakten Assurance run through Jakten Platform. Platform entitlement is derived from paid product seats; it is not assigned as a separate paid product.


3. What runs where

On your network (customer-hosted)

Data / softwareLocation
Project and risk dataYour PC or your office server
Documents and exportsSame deployment as databases
Desktop applicationEach user's Windows workstation
Platform Server (office path only)Office server or designated always-on Windows PC

On jakten.net (Northland-operated)

ServicePurposeCustomer project data?
checkout.jakten.netStripe purchase and activation key deliveryNo
licensing.jakten.netSubscription validation, activation redeem, and the Jakten AI gateway when your company turns AI onStores no project data — subscription metadata, and for AI a usage record without content
docs.jakten.netCustomer guides and legal documentsNo
[email protected]Commercial supportNo

Important: jakten.net never stores your project or risk model data. Your analytical work stays on infrastructure you control. If a company administrator turns on Jakten AI, the AI features each module lists send what that feature needs through licensing.jakten.net to Jakten's AI provider while they run; the gateway keeps only a usage record, never the content. What each feature sends is in the AI Data Handling guide of each module.


4. Standard deployment profiles

ProfileBest forSummary
Single-user (GA)One person on one PCInstall Platform on that PC; all components on that machine
Multi-user office (GA)Two or more people on separate PCsPlatform Server on office server first; desktop clients on workstations
SQL Server (planned)IT requires SQL Server operationsNot GA — documented as future release

Use Choose Your Deployment to select the correct profile before installing.


5. Activation model

RuleDetail
One activation key per company deploymentRedeem once on the deployment that holds company data (single PC or office server)
Not per userCoworkers do not activate individually on office deployments
Internet for commercial servicesOutbound HTTPS for activation, periodic validation, update checks, authorized downloads and, when turned on, Jakten AI features; daily Platform, Assurance, and Risk work remains on your deployment

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 situationRead next
One user, one PCSingle-User Quick Start
Two or more users on separate PCsChoose Your Deployment → Office Deployment Guide
Coworker (not administrator)End-User Guide
IT firewall planningNetwork and Firewall Requirements

Related documentation

GuidePurpose
Choose Your DeploymentDecision tree
Deployment diagramsVisual topology reference
GlossaryPlatform, deployment, seat, entitlement terms