On-premise deployment
Run Mithaq on infrastructure your organisation controls
What does Mithaq on-premise mean?
Mithaq has a single-tenant on-premise mode for customer-controlled infrastructure. The current source includes a Docker Compose deployment path, persistent host-mounted application data and local signed-license verification. Exact topology, network controls, backups, integrations, support and commercial terms are agreed for each deployment.
What the current deployment path establishes
The application has an explicit on-premise mode and tenant pinning. Its Compose file runs the application as a container and mounts data, content and uploads from the host. Its license verifier checks a signed local license envelope.
- Single-tenant mode selected by deployment configuration.
- Application data mounted on the selected host.
- Local license signature and validity checks.
What technical discovery must decide
On-premise is a deployment model, not a blanket security claim. The customer and Mithaq still need to agree the target platform, TLS, identity and messaging services, backup and restore, monitoring, updates and support access.
- Document required and prohibited network paths.
- Assign backup, recovery and monitoring ownership.
- Test Arabic, authentication and any optional AI services in the target environment.
How it differs from Mithaq Cloud
Cloud is the hosted SaaS route, including Mithaq subdomains and custom domains. On-premise pins one tenant to infrastructure controlled by the customer. A deployment decision should follow written governance, data and operating requirements.
- Cloud is operated as a hosted service.
- On-premise runs on the customer-controlled environment.
- Commercial and support scope is confirmed in the proposal.
Short answers
Common evaluation questions
Does Mithaq have a real on-premise mode?
Yes. The source defines an on-premise deployment mode that pins one tenant, removes SaaS billing and super-admin surfaces, and includes a Docker Compose deployment path plus local license verification.
Can it run without public-cloud hosting?
The on-premise mode is designed to run the application on customer-controlled infrastructure. Any external email, messaging or AI functions depend on the services selected and configured for that deployment.
Where is on-premise data stored?
The provided Compose path mounts application data, content and uploads from the selected host. The customer’s agreed infrastructure and backup design determine the exact physical location and copies.
What should an on-premise evaluation include?
Evaluate the target operating system or container platform, network routes, TLS, identity and OTP services, backup and restore, monitoring, update procedure, support access and recovery test. Record the agreed answers in the statement of work.
Next step
Test the workflow against your board case
Send the organisation type, board workflow and deployment requirements. The demonstration will be framed around those requirements, not an invented customer example.