EasySLU Private Install, deployed on client-controlled infrastructure.
Private Install is for companies that want EasySLU but cannot or do not want to run the accounting workspace on the standard hosted cloud. We install the software on your server, configure the production environment, and support the deployment under a clear operating agreement.
What the customer buys
A dedicated EasySLU deployment installed on client-controlled infrastructure, with setup, configuration and ongoing update support handled under a clearer operating boundary.
Plain-English deployment
Installed on your server, without making your team do the installation.
Private Install means EasySLU runs in a client-controlled environment. Founders can think of it as "installed on our server"; technical teams may call it client-hosted or on-premises.
Your company, board, client contract or internal policy requires business records to live on infrastructure controlled by the client.
You already have a VPS, private server, data center arrangement or IT partner who can own the underlying machine, access and network policy.
You need a clearer infrastructure boundary, custom backup policy, stricter access controls or a deployment that can be reviewed by technical stakeholders.
You want EasySLU installed, configured and handed over with more guidance than a self-serve cloud signup.
What you get
The same EasySLU product, with a dedicated deployment boundary.
Private Install is not a stripped-down technical package. You get the EasySLU application plus installation, configuration, update support and a clearer infrastructure boundary.
Company workflow
Invoices, receipts, document vault, bank imports, matching, accounting review, filing packs and compliance tasks remain the core product.
Installation handled
EasySLU performs the application deployment instead of handing the client a repository and asking their team to figure it out.
Environment configuration
Domain, SSL, app secrets, database, file storage, mail settings and production checks are configured as part of setup.
Client-side data location
Company data lives in the agreed client-controlled environment instead of the standard shared EasySLU cloud operation.
Scheduled updates
Updates are planned through the support arrangement so product improvements and security patches do not become unmanaged work.
Handover and support
The client receives a clear responsibility split and knows who to contact for app issues, server issues, backups and access changes.
Install process
A private deployment needs a real setup path.
Private Install is high-touch, so the process confirms the server, domain, backups, access and update model before production use.
Deployment call
We confirm company needs, server ownership, domain, backup target, access method, update expectations and who inside the client organization can approve infrastructure changes.
Server readiness
The client provides a suitable server, credentials, DNS access or IT contact. We verify the baseline before installing the application.
Install and configure
We deploy EasySLU, configure environment variables, database storage, SSL, domain routing, mail settings where needed, and operational checks.
Data and workflow setup
We create the company workspace, configure users, import starting material, connect document workflows and prepare the first review queue.
Handover and support
The client receives the operating boundary: what EasySLU maintains, what the client or IT provider owns, how updates are scheduled, and how support issues are escalated.
Pricing
Priced for installation and ongoing operational responsibility.
Private Install should not be positioned as a cheaper version of Cloud. It exists for control, policy and infrastructure requirements, so the price needs to cover installation time, support complexity, update work and server-specific troubleshooting.
Private Install
Installed on your serverFinal pricing depends on server readiness, migration scope, backup requirements, support level, integrations and whether EasySLU also manages the private server.
- Application install by EasySLU
- Production configuration and go-live checks
- Client-owned server or VPS
- Scheduled update support
- Clear responsibility handover
Cloud vs Private Install
The important difference is who owns the infrastructure.
The software experience should feel familiar in both versions. The commercial and operational difference is the hosting boundary, support model and setup effort.
Technical baseline
What needs to exist before installation starts.
A private install is straightforward when the client has a server, access, DNS and backup expectations ready. Without that, the setup becomes an infrastructure project.
Readiness checklist
- A Linux server or VPS suitable for a production web application
- Domain or subdomain access for routing and SSL
- A named technical contact or administrator for infrastructure approvals
- Backup destination and retention preference agreed before go-live
- Email, file storage and AI-provider configuration decided before production use
- Maintenance window for future updates and security patches
FAQ
Private deployment questions before the install call.
Is Private Install the same as on-premise?
For most buyers, yes. The clearer name is Private Install: EasySLU is installed on the client side, usually on a client-owned server, VPS or private infrastructure. Technical buyers may also call it on-premises or client-hosted.
Is it cheaper than Cloud?
No. Private Install requires planning, deployment, server-specific support, backup coordination and update work. It should be selected for control, data-location requirements or infrastructure policy, not to reduce the monthly fee.
Who maintains the server?
The client owns the infrastructure and server bill. EasySLU installs and supports the application under the agreed support plan. The exact operating boundary is confirmed before installation.
Can EasySLU fully manage the private server?
Yes, if that is part of the commercial agreement and the client grants the required access. That still differs from Cloud because the infrastructure is dedicated to the client and usually billed or controlled separately.
Not sure which version fits?
Cloud is the default for speed. Private Install is for control, data-location policy or existing infrastructure requirements.