Basic
€14.95 per cloud tenant and month
Set up and run it yourself.
Service details
- Self-service setup with documentation
- Tickets for technical bugs and operations issues
- Operation, updates and agreed backups of your cloud tenant
Crazy-Helpdesk & Monitoring
Helpdesk software with ticketing and monitoring.
Handle customer requests with the relevant asset and server data alongside the ticket. Monitoring, a knowledge base, and reports are included. We help you choose the right installation.
Compare plans & calculate your offer → From €14.95 per month and cloud tenant. Shared cloud is available.
Talk to us about what you need. Your inquiry is non-binding.
117 searchable features
Cloud or managed on-premises
Alert-to-ticket automation
Plans & offer calculator
Every feature. The support that fits.
Basic, Plus and Business differ in personal support, not features. Choose your support plan and optionally add exactly one SLA package.
30-day money-back guarantee.
Personal support
Plans compared
Prices net per cloud tenant and month plus statutory VAT. One-time services stated separately.
Available per cloud tenant. Tenant separation, white-label, and the separation of data and search remain subject to separate review and are not part of operational availability. Inquiry instead of ordering.
Plus
€39.95 per cloud tenant and month
Occasional personal help with using the software and standard settings.
Service details
- Everything from Basic
- Occasional personal help using the software
- Help with standard configurations
- Tickets for operation and settings questions
Business
€199.95 per cloud tenant and month
Named contact and 60 minutes per month. Unused minutes expire.
Service details
- Everything from Plus
- Named contact
- Callback and screen sharing by appointment
- 60 minutes of setup or consulting per month
- Unused minutes expire at month end; additional services by agreement
- Standard SLA included; higher SLA packages selected separately
Offer calculator
Monday to Friday, 9:00 to 17:00 Europe/Berlin, excluding public holidays. Support times apply at the contractual support location. 24/7 on-call coverage is not included.
Send a non-binding inquiry. Nothing is ordered or charged.
Product tour
Tickets stay connected to assets, alerts, and reporting.
Monitoring, self-service, and reporting extend the ticket history in the same product.
01 Ticketing
01
Ticketing with SLA, communication, and assets.
The helpdesk is more than a form. Agents see status, priority, SLA state, history, internal notes, and affected assets in one place.
- Portal, email, and guest tickets
- SLA automation and escalation
- Internal and public communication
02 Server monitoring
02
Server monitoring: alerts and tickets stay connected.
The agent sends CPU, RAM, disk, network, uptime, processes, services, and certificate state directly into the platform. Critical states become actionable service cases.
- Live metrics and history charts
- Alert rules connected to tickets
- Inventory and server context in the same screen
03 Self-service
03
Self-service with FAQ and magic links.
FAQ, public ticket creation, and magic-link access take users directly into the ticket process without an account.
- Public FAQ
- Ticket access by link
- Ticket form with required fields
04 Reporting & operations
04
Reports, deployments, and applications in one admin area.
Teams see volume, priorities, SLA trends, deployments, and the application landscape in one consistent admin area.
- Reporting with CSV export
- Deployment tasks
- Application catalog with owners
More screenshots: inventory, network, and operations
Product areas
Views across inventory, network, and operations.
Inventory, network, deployments, and application catalog provide the context when a case needs deeper analysis.
01 Dashboard
Dashboard
Open tickets, SLA state, monitoring alerts, and quick actions in one compact view.
02 Inventory & assets
Inventory & assets
Manage servers, hardware, certificates, and relations centrally.
03 Network monitoring
Network monitoring
Network values, transfer, and state directly on the server.
04 Deployments
Deployments
Roll out packages and maintenance tasks in a controlled way.
05 App compass
App compass
Keep applications, owners, and links visible.
Background, product overview, and typical workflows
Product overview
Support, monitoring, and assets stay in one work context.
The platform connects customer communication and technical operations without requiring a separate license module for every task.
Built from a real operational need
Not designed in isolation, but shaped through real operations.
The starting point was a custom vulnerability and application inventory project alongside our own need to stop spreading helpdesk, monitoring, and assets across separate tools. The result is one connected platform that has since been developed consistently in short release cycles.
Day to day, ticket, server state, and asset data live in the same record, with changes recorded in the history.
Monitoring
Technical monitoring; no 24/7 on-call coverage
Plan and operating model
One product core, with plans and support clearly separated.
No per-agent licence fee
Plans depend on support and operating model, not on the number of agent accounts.
All features in every plan
Choose how much personal help you need. The features stay the same.
Fair use instead of unlimited
Monitoring and storage are fair-use limited. Exact limits are stated in your offer.
Run by Crazy-Systems
We handle cloud operations and updates. Additional setup and migration work is agreed separately.
Controlled data location
Cloud operations in Germany or the EU, or data stored in your own infrastructure with managed on-premises.
Ticket + asset + alert
Support cases, server data, CMDB, and monitoring context stay together.
Workspaces
Three areas, one shared history.
Crazy-Helpdesk & Monitoring connects intake, analysis, monitoring, resolution, and reporting in one continuous service workflow.
Service desk
Tickets, email, SLAs, priorities, internal notes, and traceable handling in one focused workspace.
Monitoring
Server health, metrics, alerts, services, network, certificates, and hardware data next to the affected assets.
ITSM workflows
Incidents, problems, changes, approvals, rollback plans, and CMDB relations without separate tools.
Problem and response
Fewer handoffs between inbox, monitoring, and documentation.
-
01
Shared mailboxes blur responsibilities and make prioritization harder.
Queues, teams, roles, and team-based permissions create clear handling and visibility rules.
-
02
Internal IT requests and external customer issues run through different channels without a shared history.
Tickets from web, email, portal, guest forms, chat, and monitoring events become structured workflows.
-
03
Monitoring alerts, asset data, and support cases remain stuck in separate tools.
Assets, problems, changes, applications, monitoring alerts, and certificates can be linked to the case context.
-
04
Parallel license and operating costs for separate helpdesk, monitoring, or reporting tools often grow unnoticed.
Integrated monitoring can reduce or avoid the need for separate monitoring tools depending on the scenario.
-
05
Teams see too late which tickets escalate, are handled twice, or are missing knowledge.
SLA rules, business hours, escalations, notifications, and follow-ups help teams actively work open items.
-
06
Without reliable reports, backlogs, SLA risks, and staffing bottlenecks remain hard to measure.
Dashboards, reports, search, and histories make performance, bottlenecks, and dependencies visible.
-
07
Branding, self-service, and status communication are often added late and feel inconsistent.
FAQ, portal, and branding extend ticketing with self-service; personal support depends on your plan.
Direct helpdesk software comparison
Which product fits your team?
Compare ticketing, asset management, and monitoring. See what is included and where additional products are needed.
Compare 7 products by features and customer effort
In product
Plan-dependent
Integration / add-on
Separate product
Customer effort: editorial guidance for helpdesk, CMDB, infrastructure monitoring, and operations. Actual effort depends on deployment, integrations, and starting point; not a time or cost estimate.
-
01 Our productCrazy-Helpdesk & Monitoring
Ticketing, ITSM, CMDB, and integrated monitoring
Managed cloud or managed on-premises Strong when: service and operations data should stay in one work context.Core scope: Ticketing, self-service, incident, problem, and change
Rollout & operations: Product and technical operations from one team. Process configuration and data connections remain rollout tasks; personal help depends on your plan.
Feature scope in detail
- Service & ITSM
- In product Ticketing, self-service, incident, problem, and change
- Assets & CMDB
- In product Inventory, CMDB, and application compass
- Infrastructure monitoring
- In product Own agents, metrics, alerts, and service checks
- Deployment & responsibility
- Managed Cloud or managed on-premises by Crazy-Systems
-
02 Zammad
Open-source helpdesk and customer communication
Hosted or self-hosted Strong when: a flexible open-source helpdesk with multiple channels is required.Core scope: Helpdesk, channels, and workflows; SLAs depend on plan
Rollout & operations: Connect and coordinate CMDB and monitoring for the full scope. Self-hosting requires your own administration; hosted handles helpdesk operations.
Feature scope in detail
- Service & ITSM
- In product Helpdesk, channels, and workflows; SLAs depend on plan
- Assets & CMDB
- Integration CMDB connection, for example through i-doit
- Infrastructure monitoring
- Integration Alerts, for example from Checkmk
- Deployment & responsibility
- Hosted / self-hosted Vendor cloud or own operation; support plans available
-
03 Zendesk
Customer and employee service with omnichannel support and ITSM
Cloud platform Strong when: customer or employee service in a broad SaaS ecosystem matters most.Core scope: Customer and employee service including ITSM
Rollout & operations: SaaS handles platform operations. Plan selection and connections for asset context and monitoring still need planning.
Feature scope in detail
- Service & ITSM
- Plan-dependent Customer and employee service including ITSM
- Assets & CMDB
- ITAM by plan IT asset management; CMDB is not identified as a core capability
- Infrastructure monitoring
- Integration Third-party marketplace app, for example Server Monitor
- Deployment & responsibility
- Cloud No self-hosted option
-
04 Freshdesk
Cloud customer service with automation and AI
Cloud platform Strong when: customer service and automation are the priority.Core scope: Customer support and ticketing
Rollout & operations: SaaS handles Freshdesk operations. For ITSM, CMDB, and ITOM, also plan for Freshservice and alignment between products.
Feature scope in detail
- Service & ITSM
- In product Customer support and ticketing
- Assets & CMDB
- Separate product ITAM and CMDB through Freshservice
- Infrastructure monitoring
- Separate product ITOM and service health through Freshservice
- Deployment & responsibility
- Cloud Freshdesk is delivered as SaaS
-
05 Jira Service Management
ITSM, assets, and service workflows close to development and operations
Cloud or Data Center Strong when: Jira and Atlassian are already central to the organization.Core scope: Cloud: request and incident in the core; problem and change in Premium / Enterprise. Data Center has a different scope
Rollout & operations: Configure the platform, assets, and monitoring connections. Cloud and self-managed Data Center differ in scope and operating responsibility.
Feature scope in detail
- Service & ITSM
- Plan-dependent Cloud: request and incident in the core; problem and change in Premium / Enterprise. Data Center has a different scope
- Assets & CMDB
- Plan-dependent Plan-dependent in Cloud; included in Data Center
- Infrastructure monitoring
- Metrics via integration Cloud: alerting and on-call in the product; metrics and events from connected monitoring and logging tools
- Deployment & responsibility
- Cloud / Data Center Atlassian-hosted cloud or self-managed Data Center
-
06 ManageEngine ServiceDesk Plus
ITSM, asset management, CMDB, and enterprise service management
Cloud or on-premises Strong when: conventional ITSM and asset management need broad coverage.Core scope: Helpdesk and ITSM processes
Rollout & operations: Align editions and ITOM components. On-premises also requires your own administration; cloud handles platform operations.
Feature scope in detail
- Service & ITSM
- Edition-dependent Helpdesk and ITSM processes
- Assets & CMDB
- Edition-dependent ITAM and CMDB; scope depends on edition or add-ons
- Infrastructure monitoring
- Add-on / integration For example OpManager, Applications Manager, or Site24x7
- Deployment & responsibility
- Cloud / on-premises SaaS or own operation
-
07 ServiceNow
Enterprise platform for IT services, workflows, and automation
ServiceNow Cloud; Private Stack as a special model Strong when: an organization-wide platform and workflow strategy is required.Core scope: ITSM and enterprise workflows
Rollout & operations: Plan rollout as an enterprise platform project. Align ITSM, ITAM, and ITOM plus responsibilities for cloud or Private Stack.
Feature scope in detail
- Service & ITSM
- Plan-dependent ITSM and enterprise workflows
- Assets & CMDB
- In product Asset management and CMDB; advanced ITAM modules are separate
- Infrastructure monitoring
- Additional module ITOM AIOps, Event Management, and Observability
- Deployment & responsibility
- Cloud / special model ServiceNow Cloud; Private Stack is operated by the customer or a partner
Compare other providers and their strengths
-
Open-source helpdesk
Zammad
Strong forFlexible helpdesk with strong communication channels plus hosted and self-hosted deployment.
Why Crazy CMDB and infrastructure monitoring require additional systems that must be connected and coordinated in operation. With Crazy, tickets, assets, alerts, and technical operations belong to one managed system from the start. -
SaaS service
Zendesk
Strong forEstablished customer and employee service with a large SaaS and marketplace ecosystem.
Why Crazy Technical asset context and infrastructure monitoring are added through plans or integrations. Crazy connects both directly to the ticket and also takes responsibility for operations. -
Customer service
Freshdesk
Strong forAccessible cloud customer service with ticketing and automation.
Why Crazy Covering ITSM, CMDB, and ITOM leads to Freshservice and further product decisions. Crazy keeps service desk, assets, and monitoring in one product core. -
Atlassian ITSM
Jira Service Management
Strong forStrong ITSM and development/operations workflows when Jira and Atlassian are already established.
Why Crazy Without an existing Atlassian standard, plan selection, configuration, and monitoring connections can become a platform project of their own. Crazy starts with a tighter scope and includes managed operations. -
IT management suite
ManageEngine ServiceDesk Plus
Strong forBroad conventional ITSM and asset management with cloud and on-premises options.
Why Crazy Editions, additional products, and ITOM connections need to be aligned for the full scope. Crazy uses one product core and one accountable operations team. -
Enterprise platform
ServiceNow
Strong forA powerful platform for organization-wide workflows, governance, and automation.
Why Crazy ServiceNow is quoted individually and designed for a broad enterprise framework. Crazy offers shared cloud with transparent per-tenant pricing; we agree rollout scope and personal support first.
How tickets, assets, and operations work together
Tickets with context
Ticket, asset, and operations stay connected.
See the affected assets and monitoring events alongside the ticket, without switching between tools.
Explore every feature-
01
Requests & communication
Portal, email, guest access, live chat, and FAQ
-
02
Tickets & service processes
Queues, SLAs, incidents, problems, and changes while tickets, assets, and alerts stay connected
-
03
Assets & system context
CMDB, applications, inventory, and certificates
-
04
Monitoring & operations
Own agents, metrics, alerts, and service checks. Monitoring is part of the product; scope follows the fair-use limits in your offer
-
05
Managed by Crazy-Systems
Managed cloud or managed on-premises; product, updates, and technical operations from one team
Next step
Does Crazy-Helpdesk fit your team? Let’s get started.
Team size, preferred start, and operating model are enough for the first step. We will work out the rest together.
Reviewed 16 July 2026. The comparison uses published product information. Effort estimates cover setup, integrations, and operations, not general usability. Actual effort depends on your environment and project. Prices are not compared.
View official product pages
All features
All features by workspace.
The list covers ticketing and monitoring through CMDB, self-service, reporting, and administration.
No matching feature found. Change the search term or reset the filters.
01 Ticket and incident management Full ticket system for support, incidents, and operational requests. 15 features
- Ticket intake via web, email, phone source, and monitoring events
- Custom ticket numbers with a freely configurable prefix
- Status, priority, type, and queue control
- Assignment to agents and teams
- Custom fields including required fields and team-specific fields
- Privacy and consent fields with evidence logic
- SLA due dates for response and resolution times
- Queue-specific SLA policies by priority
- Internal and external comments
- File attachments on tickets and comments
- Links between tickets, problems, and changes
- Master and sub-ticket logic
- Bulk actions, follow-ups, and escalation rules
- History of relevant ticket changes
- Deletion request workflow for controlled ticket removal
02 Email integration Incoming and outgoing emails are processed directly in the ticket workflow. 8 features
- IMAP, POP3, and Microsoft 365 mailboxes
- Automatic ticket creation from incoming emails
- Ticket updates via email replies
- SMTP sending for replies and notifications
- Default and team-specific sending accounts
- Defaults for queue, priority, and ticket type on email import
- Auto-close keywords for defined replies
- Logging of email processing
03 Self-service, portal, and FAQ Portal, guest access, and knowledge base reduce direct support requests. 12 features
- Customer portal for signed-in end users
- Overview of own tickets, ticket creation, and detail view
- Public FAQ as an entry page
- Guest ticket form without login
- Time-limited magic link for guest access
- Configurable landing page for visitors
- FAQ categories with subcategories
- Visibility for public content, customers, or agents
- German and English content
- Search and suggestion features
- Helpful / not-helpful ratings
- Ticket creation directly from matching FAQ articles
04 Live chat Direct first contacts and quick follow-ups in the same service context. 6 features
- Chat for guests and users
- Agent dashboard for waiting and active chats
- Availability status for agents
- Stored chat histories
- Text snippets for agents
- Converting a chat into a ticket
05 Problem and change management Root cause analysis, known errors, changes, and approvals stay traceable. 12 features
- Standalone problem records
- Linking multiple tickets to one problem
- Root cause analysis fields and workaround documentation
- Known error marking and KEDB content
- Change capture for standard, normal, and emergency changes
- Priority and risk assessment
- Planning window for start and end time
- Business case, implementation plan, test plan, and rollback plan
- CAB members and voting logic
- Approvals with approve, reject, and comments
- Links to tickets, problems, and assets
- Change calendar, change reports, and history tracking
06 App compass and application catalog Applications, responsibilities, and technical references become visible in one place. 9 features
- Central application catalog
- Categories, short and long descriptions
- Status control for active, inactive, and maintenance
- Responsible persons and app managers
- Documentation and support references
- Logos and visual marking
- URL and deep-link templates with placeholders
- Links from applications to inventory assets
- Permission control for maintaining individual applications
07 Inventory and CMDB Technical objects, responsibilities, relations, and lifecycle data in one module. 16 features
- Servers, PCs, laptops, VMs, network devices, software, mobile devices, printers, and other items
- Custom inventory numbers and status management
- Network, operating system, and hardware data
- Multiple IP and MAC addresses per asset
- Location, team, and person assignment
- Technical contact (TechAP), deputy, and contact information
- External ticket and change references
- Warranty and lifecycle data
- Links to tickets, problems, changes, and app compass
- CMDB relations between assets
- Change history and deletion request workflow
- Dashboard and family views
- Bulk assignment for teams and groups
- Certificate management with detail view and download
- Import of audit reports, Microsoft Defender, and external inventory data
- Tracking of installed software on assets
08 Monitoring & operations Agent-based monitoring with alerts, tickets, remote actions, and deployment functions. 15 features
- Server registration with approval workflow
- Heartbeat monitoring and online / offline detection
- Live views and historical metric snapshots
- Role-based assignment of monitoring servers
- Alert rules for teams, roles, individual servers, or globally
- Automatic ticket creation from alerts
- Exceptions per rule and server
- Manual processing and resolution of alerts
- CPU, RAM, swap, disk, disk I/O, network, and interfaces
- Open ports, services, top processes, uptime, and user sessions
- Windows event logs, HTTP checks, IIS, Apache, Tomcat, PHP, and MSSQL
- Remote actions: ping, service control, restart, agent update, and uninstall
- Deployment packages with target paths, exclusions, and service control
- Deployment and removal jobs with status tracking
- Integration points for PRTG Network Monitor and Microsoft SCOM
09 Notifications, reporting, and administration Operations, reporting, permissions, and system control are covered directly in the product. 15 features
- Notification channels for email, Microsoft Teams, SMS, and Discord
- Team-specific or global channels
- Templates with placeholders for tickets, changes, problems, monitoring, and chat
- Preview, send tests, and delivery logs
- Ticket SLA, alert, chat, and workflow notifications
- Reporting dashboard and ticket, SLA, agent, problem, and change reports
- Trend data over time ranges
- CSV exports for tickets, problems, and changes
- Local user management and role-based permission model
- Freely maintainable roles, permissions, and teams
- Password change, password reset, and user activation
- Audit log for traceable changes
- Branding with logo, favicon, colors, page title, and footer
- System settings for ticket prefix, attachment size, SLA, and monitoring
- Insight into background jobs and schedules
10 Authentication and languages Local login, LDAP, and multilingual interfaces are planned for production use. 9 features
- Local user accounts
- LDAP / Active Directory login
- Attribute synchronization at login
- LDAP group mapping to service desk roles
- Azure AD / Microsoft Entra ID, SAML 2.0, and OAuth2 / OIDC technically prepared
- Interface and content support for German and English
- Bilingual FAQ and ticket custom field labels
- Customer-side branding
- Public pages for FAQ, imprint, and privacy
Use & operation
Does Helpdesk fit your team?
Find suitable use cases and the next steps for rollout.
Support models
For internal IT, business customers, and end users.
The platform is not limited to one support model. Portal, roles, teams, FAQ, monitoring, and reporting can be combined for different audiences.
B2B service desk
For IT providers, hosting companies, and technical teams that handle customer requests, assets, alerts, and escalations together.
- Roles and teams
- Customer-facing communication
- Technical ticket context
B2C and end-user support
Portal, FAQ, guest tickets, and magic-link access support structured communication without complex account setup.
- Self-service and FAQ
- Guest ticket intake
- Status communication
Use cases
Where ticketing, assets, and monitoring are needed together.
Depending on the rollout goal, the platform can act as a service desk, operations workspace, or customer-facing support environment.
More use cases
Internal IT service desk
Employee requests, incidents, hardware / software context, SLA control, and team assignment.
Software customer support
Portal, FAQ, guest access, email processing, and status communication for external users.
Managed service providers
Technical alerts, customer requests, assets, reporting, and team responsibilities in one system.
Hosting and infrastructure support
Monitoring agent, service monitoring, certificates, inventory, deployments, and status communication.
Public-sector organizations
Privacy-oriented positioning, German support, audit log, role rights, and traceable processes.
Industry and technical services
Connect service requests, asset context, monitoring, reporting, and change / problem workflows.
Rollout process
From agreed scope to production use.
We align requirements, roles, and data sources first, then expand the operation step by step.
View rollout steps
Review requirements
Teams, channels, roles, and data are recorded and prioritized.
Choose operating model and scope
Shared cloud is available. We discuss the right support and agree rollout scope in your offer.
Provision the system
Crazy-Systems sets up the agreed operating model and handles technical administration.
Configure processes, roles, and branding
Queues, SLAs, users, teams, templates, portal, FAQ, and notifications are adapted.
Connect data and integrations
Email, monitoring, asset data, reporting, and relevant integrations are connected by project.
Go live and extend
After launch, monitoring, reports, changes, or migration paths can be expanded.
Operating models & security
Shared cloud tenant, own instance, or on-premises.
Shared cloud is available. Responsibilities for updates, maintenance, monitoring, and changes depend on the operating model. We agree an own instance and on-premises individually.
FAQ
Common questions before rollout.
Answers about ticketing, server monitoring, pricing, and operations.
What is helpdesk software with a ticketing system?
A ticketing system records support requests as individual cases with a status, owner, and history. Crazy-Helpdesk adds self-service, assets, ITSM workflows, and server monitoring to that workspace.
Who is Crazy-Helpdesk & Monitoring for?
IT providers, hosting companies, and internal or external support teams that handle requests alongside technical system context. Roles and teams, an end-user portal, public FAQ, guest tickets, and magic-link access support B2B, B2C, and mixed models.
What does the helpdesk software cost and how do the plans differ?
From €14.95 per month and cloud tenant. Shared cloud is available. Cloud prices are net, excluding VAT. Every plan includes all features, with no per-agent licence fee. Basic is self-service for software configuration. Plus offers occasional personal help; Business includes a named contact and 60 minutes per month. Unused minutes expire. Additional setup and migration work is agreed separately; own installations require an individual offer.
Is the helpdesk software available in the cloud or on-premises?
Shared cloud is available as a managed cloud solution in Germany or the EU. We agree an own instance and managed on-premises individually; data location, hosting, updates, and backups are confirmed in the agreed operating scope before setup.
How does ticketing connect support with server monitoring?
Monitoring agents deliver server metrics; alert rules can automatically create tickets from them. Affected assets, server data, and alert context stay connected to the service case. Monitoring and storage follow the fair-use limits agreed in your offer.
Which integrations are confirmed?
Confirmed integrations include IMAP, POP3, Microsoft 365 Graph, SMTP, Microsoft Teams, SMS, Discord, PRTG, Microsoft SCOM, and the monitoring agent API.
Are migration options available?
Migration paths and tools are prepared for typical legacy systems and structured data sources. We review what can be transferred based on your source system.
Are tenant separation and per-tenant white label confirmed?
Shared cloud is available. This does not automatically confirm technical tenant separation, search isolation, or per-tenant white label; we review those properties separately.
Start with Crazy-Helpdesk or see it live first.
For a direct start, tell us your team size, operating model, and preferred timing. In a demo, we show ticketing, monitoring, and CMDB in a concrete workflow.