Every feature, honestly catalogued
117 features across 20 categories. Rust on the backend, Vue on the frontend, all of it open source.
What sets Nosdesk apart
Most helpdesks bolt these on as add-ons. We build them in, and wire them together.
Tickets
The core helpdesk surface, with a three-column desktop layout and structured metadata.
- Ticket lifecycle
- Categories with group-scoped visibility
- Assignment rules
Documentation & knowledge base
A collaborative wiki that knows about your tickets.
- Collaborative editor
- Hierarchical pages with collections
- Page verification with expiry
Knowledge gaps queue
An editorial backlog driven by real ticket and search demand.
- Two-table signal model
- Manual flagging
- Cluster detection
Plugins & extensibility
Ed25519-signed plugin bundles with a three-tier trust model.
- Signed plugin bundles
- Plugin registry
- Plugin slots in the UI
Full feature catalogue
Browse by area. Each category page lists every shipping capability, what's partial, and what's planned.
Authentication & identity
Four authentication paths plus session and security telemetry.
Languages & localisation
Five locales, per-user language and timezone, and timezone-aware SLAs.
Channels & multi-source intake
Tickets can come from any channel without losing their provider metadata.
Asset & device management
A general asset catalogue, with deep device management on top: Intune sync, groups, and ticket linkage.
Users, teams & groups
Three-tier RBAC with hierarchical group includes.
Real-time & collaboration
SSE topic bus with replay buffer, plus Yjs awareness.
Search
Tantivy full-text search across every entity.
Integrations
Microsoft Entra, Microsoft Graph, IMAP/SMTP, and S3 storage.
Notifications
In-app feed plus email delivery, with per-event preferences.
Webhooks
Outbound webhooks with delivery log and manual retry.
Dashboard & personalisation
12 widgets, drag-drop reorder, and sparse stats endpoints.
Branding
Custom logo, colours, and organisation name per instance.
Guest access & public portal
Public ticket submission and a read-only documentation portal.
Administration
Everything a sysadmin needs, on one sidebar.
Backup & restore
Full snapshot export and restore, integrated into onboarding.
Security & compliance
Rate limiting, CSP, encrypted secrets, and a sandboxed email renderer.
Architecture worth talking about
Choices that don't show up in feature lists but matter once you've been using the product for a few weeks.
Tickets and docs share a database
A many-to-many join means every doc page can list the tickets it resolved, and every ticket can list the docs that closed it. We looked, and no other helpdesk we tried actually models this.
Channel metadata stays attached, end to end
Every comment carries from_address, external_id, and the provider-specific refs that came in with it. Replying through a different channel still has the original context.
Page verification as a trust primitive
A doc says "verified by X, valid until Y" with a stale-state UI when it expires. Same data is what AI grounding will rank against later.
Knowledge gaps with structured signals
Manual flag, ticket cluster, and failed search all land in one queue with a uniform schema. The LLM phase reads from this without needing a migration.
Yjs CRDT collaborative editing
Real cursors, real undo across users, no merge conflicts. The same Yjs stack you find in Notion and Linear.
Plugin trust chain backed by Ed25519
Three trust tiers (official, verified, community) with explicit registry distribution. The signing chain is real, not a future "we'll add auth later" placeholder.
Be first in line
Join the waitlist and be among the first to experience a helpdesk that keeps up with you.