01Mulify Dedicated
Your domain. Your infrastructure. Powered by Mulify.
Mulify Cloud runs on infrastructure Mulify operates. Mulify Dedicated is the same application, installed for one organization on infrastructure that organization owns — your cloud account or your VPS — and reached at your own address, such as inventory.yourcompany.com.
It is not a custom domain bolted onto a shared system. It is a dedicated deployment, configured and maintained by us on infrastructure that stays yours.
- Installation
- Dedicated, yours alone
- Infrastructure
- Your cloud or VPS
- Address
- Your own domain
- Deployed by
- Mulify
- Commercial
- Agreed per deployment
02The arrangement
Where everything sits
One installation, on infrastructure you own, reached at your own address. Mulify operates the application inside that boundary — it does not own the boundary.
Your account · your boundary
01
Your domain
inventory.yourcompany.com
The address your team and your partners use. DNS stays under your control.
02
Your cloud or VPS
An account you own
The machine the application runs on, billed to you by your own provider.
03
Mulify Envanter
A dedicated installation
The same application as Mulify Cloud, installed and maintained here by us.
04
Your data
Catalog, media, stock, partners
Records and photography held on your infrastructure, under your control.
03How it works
From your account to live
Five steps. Nothing is automated on your behalf: a dedicated deployment is set up with a person, in the order below.
01
Choose your infrastructure
Your own cloud account or VPS. You keep the account, the access and the billing relationship with the provider.
02
Connect your domain
A domain you own — inventory.yourcompany.com, for example. DNS stays under your control.
03
Mulify configures and deploys
We install Mulify Envanter on that infrastructure and configure the application for your organization.
04
Validation
The deployment is checked end to end — sign-in, the workspace, media, and the modules you are using — before anyone works in it.
05
Go live
Your team signs in at your own address, and the application is maintained under the support arrangement agreed with you.
04Responsibility
Who carries what
Worth reading before anything is agreed. A dedicated deployment divides the work, and this is the line.
You
What stays with the customer
- The cloud or VPS account
- Infrastructure billing and any third-party costs
- Domain ownership and DNS
- Who inside your organization has access
Mulify
What Mulify carries
- Deploying the application to your infrastructure
- Configuring Mulify for your organization
- Application updates under the agreed support arrangement
- Troubleshooting the Mulify application itself
Support levels and response times are part of the arrangement agreed with you. Mulify publishes no round-the-clock guarantee, and does not take ownership of, or responsibility for, your infrastructure.
05Cloud or Dedicated
The same application, two arrangements
Identical software. What differs is where it runs, whose address it answers on, and how it is paid for.
| Aspect | Mulify CloudWe host it | Mulify DedicatedYou host it |
|---|---|---|
| Runs on | Mulify infrastructure | Your cloud or VPS |
| Address | A Mulify address | Your own domain |
| Installation | Shared platform | A dedicated installation |
| Commercial | Monthly or yearly subscription | Arrangement agreed per deployment |
| Setup | Immediate, self-serve | Configured and deployed with you |
| Infrastructure cost | Included in the subscription | Billed to you by your provider |
06Next step
Talk it through
A dedicated deployment starts with a conversation about your infrastructure, your domain and how your team works — not with a checkout.
A contact route for dedicated enquiries is being set up. Until it is published here, a dedicated deployment is arranged directly with Mulify through your existing contact with us.