Live overview
System healthy, active tenants, last sealing, last login, at a glance instead of in the log file.
One shared server for your apps and business data. Choose your hardware or hosting provider and manage tenants, access and system status centrally. The infrastructure stays your choice.
Export business data in open formats. The ZIP export keeps data from sales, purchasing, accounting, payroll, inventory and projects usable outside the app. Your IT team can use it for archiving or a planned migration.
The server comes with a full operations console: status and load, tenants, license, versions, updates, backups, logs and audit. Sign in with an administrator account, cleanly separated from the ERP, just as you know it from mature server software.
System healthy, active tenants, last sealing, last login, at a glance instead of in the log file.
Tenants, administrators and license status directly visible, without a database tool.
A new version in one click: self-check, health gate and automatic rollback on failure.
The audit log records changes in a verifiable chain. Integrity checks and supporting records help your team and auditors trace operations. Closed periods, VAT rates and reporting status remain visible.
Solid foundations instead of a tinkered solution, so the server simply runs.
A complete tenant backup at the push of a button, stored persistently, your data is secured.
A version change with a health gate and automatic rollback, never a half-installed system.
A database-independent recovery tier brings the server back, even when the database is stuck.
License status, edition and installed versions visible and traceable at any time.
Several tenants cleanly separated on one server, ideal for groups and fiduciaries.
A searchable log for each tenant shows who made which change and when. The audit chain can be checked for integrity.
With ewws, data sovereignty is not a marketing word but built in.
Runs on your server, locally or in the data center of your choice, under Linux, macOS, Windows or as Docker.
Export to CSV plus a byte-exact backup (pg_dump): your data is never locked away.
Document retention, audit records and electronic reporting functions support Swiss SMEs and their fiduciaries.
Data sovereignty is only half the story. The server is hardened against attacks and carries a whole team's daily work with room to spare.
Access requires valid authentication. Repeated failed attempts trigger longer waiting times, making automated password guessing harder.
Every tenant sees only its own data. The separation is enforced from the signed sign-in, not from values a client can change. Ideal for groups and fiduciaries with multiple tenants.
Configure HTTPS with suitable certificates for your apps to connect. The setup determines how the server is reached and which network access is allowed.
The number of workstations, data volume and everyday workflows determine the right server setup. Plan capacity with your IT team around your business and its expected workload.
The operations console shows the condition and utilisation of your installation. Your IT team can use this information to identify bottlenecks and adapt the environment to your workflows.
As user numbers or data volumes grow, you can adapt your infrastructure. Your IT team plans storage, database and server resources around demand.
An ERP knows salaries, purchase prices and margins. Access in ewws is therefore not a matter of courtesy but a matter of rule: finely divided, enforced on the server and recorded in both directions.
Roles
Every company file comes with six ready-made roles: administration, accounting, operations, read-only, human resources and employee self-service. Beneath them lie more than 150 individual rights from which you build your own roles. Viewing, editing, posting, approving and triggering are each a right of their own, not one master switch.
Sessions
When a password is set or an account is deactivated, the live sessions of that account end immediately. Access you withdraw is withdrawn, not merely due to expire. Repeated wrong sign-ins slow the account down, each time for longer.
Fiduciary access
A fiduciary office sees a client file only with that client’s grant, and the grant is an act of the client, not of the office. It names the rights one by one, it can never carry administrative rights, and both sides read in the log who did what and when.
Modules
What you switch off for a company file disappears from the navigation on the Mac and under Windows, and on every device it can no longer be reached through the address either. The server refuses the request and says where you can switch the module back on. That way every client gets exactly the product they ordered.
Your IT team prepares the server, database, network access and backups. Web setup and the server console then guide product configuration. Establish responsibilities and running costs before launch.
Step 1
You install the service on Linux, macOS, Windows or as a container and configure it in the web setup. From then on it runs as a system service and starts with the machine, with nobody having to leave a window open.
Step 2
You create the first company file and store the licence file. It is signed and verified without a network connection. The edition decides the functional scope, the module activation decides what a single company file sees of it.
Step 3
Backup and update run from the operations console. A version change checks itself and rolls back on failure instead of sitting there half applied. The secrets of your banking and eBill connection are stored encrypted in the database, never in clear text.
The architecture behind ewws: native clients, separated tenant data, secure updates.
View technology →Salary reporting, GeBüV and VAT: compliance that is in the product, not in the brochure.
View standards →How to set up the ewws server, from web setup to a running service.
View installation →Decide where your server will run, who will maintain it and which apps your team will use. The installation guide walks you through setup.