Infronest documentation
Everything you need to launch your workspace, add your team, turn on the modules your plan includes, and connect Infronest to the rest of your stack. Each Infronest customer runs in an isolated, tenant-scoped workspace on its own subdomain.
Getting started
Creating a workspace takes three steps. From the pricing page or a demo, start sign-up and you will move through:
- Company info — your company name, your full name, work email, and a password. The company name becomes your workspace address.
- Choose a plan — pick the plan that matches the modules you need. Plans decide which modules your organization can turn on.
- Verify email — confirm your address. Your account stays inactive until the email is verified.
Your workspace lives at a dedicated subdomain derived from your company name — for example a company named “Acme Corp” gets acme-corp.infronest.com. That subdomain is your tenant boundary: sign-in, branding, data, and the modules you see are all scoped to it. A short list of reserved names (such as www, api, auth, admin) cannot be used as a workspace slug.
The account you create first is your workspace Super Admin. From there you invite the rest of your team and assign each person a role (covered below).
Signing in and sessions
Sign in at your workspace subdomain. Infronest issues short-lived JSON Web Tokens on a successful login — a browser session is kept fresh automatically, and the same tokens back the desktop, mobile, and PWA apps. Access tokens are short-lived (60 minutes by default) and are silently refreshed, so you are not asked to log in repeatedly during normal use.
Privileged roles are required to protect their account with two-factor authentication (TOTP). When 2FA is enabled, the password step is followed by a one-time code before full access is granted, and you can generate backup codes in case you lose your authenticator. Brute-force protection and per-user concurrent-session limits are enforced automatically.
For programmatic access, the same login endpoint returns tokens you can send as a bearer header. See the API reference for the exact request and response shapes.
Tenant administration
Infronest is multi-tenant by design. Every user, asset, ticket, device, and report belongs to a single organization, and the platform scopes all data to the signed-in user’s organization — one tenant can never see another tenant’s data. As a Super Admin you manage three things:
Your workspace profile, branding, and the dashboard preset your team sees.
Invite teammates, deactivate leavers, and assign each person a role and department.
Control exactly which modules and actions each role can reach with granular permissions.
Roles and permissions
Access is governed by role-based access control. Every user carries a role, and permissions are scoped to the modules your organization actually has. The built-in roles are:
The Infronest platform-owner account. Sees every module and the internal Owner control panel. Reserved for the SaaS operator, not tenant staff.
The first account created for your workspace at sign-up. Full administrative control over your organization: users, roles, modules, and settings.
Day-to-day administration across the modules your plan includes, without the workspace-owner powers reserved for Super Admin.
Operational access to IT tooling — assets, tickets, endpoints, patching and monitoring — scoped by the permissions you grant.
Access aimed at pipeline, deployment and server-provisioning workflows.
Read-only visibility for auditors and stakeholders who need to see but not change data.
Self-service access: an employee sees their own assigned assets, their tickets, and their purchase requests via the employee dashboard.
Scoped access for managing marketing blog content only.
Beyond the role, you can grant or restrict individual module permissions per user, so two people with the same role can still have different reach.
Module configuration
Infronest ships as roughly forty modules — one per sellable capability. Your plan decides which modules your organization can enable, and a workspace owner can be granted extra modules beyond the plan when needed. Turn a module on and it appears in the sidebar for the roles that have access. Each module has its own product page with setup detail:
Apps and agents
Infronest runs in the browser and also ships as a desktop app (Windows, macOS, Linux via Electron), a mobile app (Android and iOS via Capacitor), and an installable PWA. For device management and patching, lightweight agents are enrolled onto the endpoints you manage — Windows, macOS, Linux, and Android — plus a standalone patch agent that runs without the full MDM stack.
Grab the apps and the enrollment agents from the download page. Enrolled agents talk to your workspace over authenticated, backward-compatible endpoints.
For developers
Every module is backed by a REST API scoped to your workspace at https://<workspace>.infronest.com/api/. Authenticate once with your workspace credentials, then call the module endpoints with a bearer token:
curl -X POST https://<workspace>.infronest.com/api/auth/login/ \
-H "Content-Type: application/json" \
-d '{"username": "you@company.com", "password": "••••••••"}'The full authentication flow, base-URL rules, and the real endpoint groups (with request and response shapes taken directly from the live OpenAPI schema) live in the API reference.
Want a guided walkthrough of your rollout? Our team will map your modules and users with you.