Questions & Answers

Eviworx is self-hosted — you run it in your own infrastructure (on-premise or your private cloud). There is no SaaS offering and no storage in third-party clouds; your data stays with you. Deployed as Docker containers (Docker Compose), multi-instance ready.

Billing is by active agents — staff members who work on tickets. End users / requesters, tickets, assets and all modules are unlimited and included at no surcharge. Editions differ only in support & operations, not in features.

Every change is logged in a SHA-256 chain (prevHash, blockchain-like) and protected by a database trigger: tampering with one entry breaks the chain and is detectable. Sensitive fields (passwords, tokens) are redacted automatically and personal data is detected.

Zero-trust: the AV worker has NO file access and only passes paths to the scanner (ClamAV), which reads from a read-only volume. Infected files are automatically moved to an isolated quarantine volume; signatures are updated continuously.

Entra ID SSO (OAuth 2.0, group-to-role mapping), Microsoft Teams (Bot Framework) and Cisco Webex for notifications, multi-mailbox (IMAP/SMTP + Microsoft Graph API), webhooks with SSRF protection and a documented REST API with API keys.

A unified approval system with four strategies (ALL/ANY/MAJORITY/QUORUM), deadlines per approval, four-eyes principle (requester ≠ approver) and conditional auto-approval. Incidents have a closure-approval flow, P1/P2 a mandatory PIR.

Closed items can be reopened in a controlled way — with a configurable reopen window, mandatory reason and limit plus a dedicated permission. Plus auto-close of inactive tickets, auto-resolve of unanswered waiting-customer tickets, stale reminders across all domains and reopen analytics.

Yes. A ticket can have sub-tickets — one level deep, each assigned to a single parent ticket. The parent ticket cannot be resolved while a sub-ticket is open and pauses its SLA during that time (can be switched off per SLA policy). The assignee of the parent ticket is notified when a sub-ticket is resolved or reopened; requesters do not see the internal breakdown — it depends on the permission for internal ticket details. Reports can filter and sort by parent ticket and by the number of sub-tickets.

Yes, completely — tickets, assets and audit logs as CSV/JSON/PDF, plus direct PostgreSQL access (on-premise) and the REST API. No vendor lock-in.

Eviworx supports you with architecture and processes in meeting GDPR and NIS2 requirements (data sovereignty, encryption, role model, continuous audit history, integrated data-breach flow). This does not constitute a certification or a legally binding declaration of conformity.

Typically 4–8 weeks: setup (~1 week), onboarding & training (~2 weeks), production operation with feedback (2–4 weeks), then the go-live decision. 30 days free, no credit card — container deployment accelerates the start significantly.

Standard support (email/portal) is included in every license. Response times and a dedicated contact depend on the edition (see pricing). Premium support with shorter response times is bookable separately.

For IT departments and managed service providers in the mid-market (roughly 5–100 agents), especially in compliance-oriented and regulated industries (healthcare, manufacturing, energy, public sector) with on-premise requirements.