a controlled runtime with a plannable lifecycle
Technology that gives you control over data, operation and the future.
Java 25, PostgreSQL, native desktop operation and open Swiss financial standards. You decide where your data lives and who runs operations.
relational data storage without a license trap
data sovereignty stays with you: self-hosted or public cloud
Clean/Hexagon/DDD
Business logic lives in the domain core. UI, database, server and external interfaces stay adapters. This lets modules be extended, tested and operated, without binding professional rules to surfaces or infrastructure.
Why built this way
Nine architecture decisions that protect you for years.
Every decision in ewws follows a clear line: control over data, operation and the future. The architecture stays traceable and designed for long-term stability.
Data sovereignty
Your data lives where you decide, in your data center or in your own public cloud account. This keeps you in control of operation and data storage.
Native desktop instead of browser
Power users work in ewws every day. The native Mac app offers keyboard control, multiple windows and direct operation, designed for continuous use.
PostgreSQL as the foundation
A proven relational database without license costs. Flyway makes every schema change reproducible, backups stay portable, even after many years.
Deployment by choice
Self-hosted or public cloud: the same build, the same codebase, the same license. A change of operating model means neither a new product nor a new integration.
Open Swiss standards
QR-bill, ISO 20022, Swissdec and eBill provide reliable standards. Entry, growth and interfaces stay predictable, even when the market environment changes.
Longevity and stability
Java as an LTS platform and a controlled release cycle create predictability. The server is written in direct Java 25, without Spring Boot or a comparable framework stack, so startup, memory footprint and dependency chain stay manageable. This keeps ewws a stable operating topic and not a constant migration project.
Controlled licensing and updates
Licensing, activation and updates run signed and traceable. This keeps edition, modules and versions clearly managed, without changing productive installations in an uncontrolled way.
A shared data foundation
CRM, finance, inventory, projects, service and the iOS app work on the same professional basis. Information is not moved between isolated solutions, but used where it is needed in the workflow.
Chosen deliberately
Why direct Java 25, no Spring Boot or comparable framework stack.
The ewws server runs on pure Java 25 with its own composition root, without Spring Boot, Quarkus or a comparable framework container. Four reasons stand behind the decision and shape operation from day one.
ScopedValue instead of framework magic
Tenant separation runs via Java 25 ScopedValue, visible in the code and in every stack trace. No hidden ThreadLocal swap, no annotation that the container interprets, no implicit behavior. Whoever wants to read the tenant context sees in one line who set it.
Its own composition root
Dependencies are wired explicitly in the bootstrap, not fished from the classpath via @Autowired. Every connection from domain to application to persistence is in one file and is reproducible one-to-one in tests. This makes Clean Architecture and the hexagonal pattern strictly sustainable, without framework helpers that allow shortcuts.
Fast startup, small attack surface
Without reflection-based bean wiring, the server starts in seconds instead of dozens of seconds. The transitive dependency chain stays small, fewer libraries mean fewer CVE updates and shorter audit chains. What is not in the server cannot be attacked.
Operationally simple
One JAR file, one LaunchAgent or systemd service, no Spring Cloud Discovery, no config server, no service mesh as a requirement. For an SME operation with ten to a hundred users, direct Java code is enough. Scaling happens through clear modules, not through additional infrastructure components.
Updates like a Mac app
A new version via a banner in the app, one click, SHA-256 verified.
Updates are signaled via a server manifest. The ewws Mac app checks daily, shows a banner with the version number and changes, and installs the signed build with SHA-256 verification. Like macOS system updates, not like forced cloud updates.
A server manifest controls distribution
The ewws server provides a manifest at /releases/desktop/latest. A version branch can be fixed per tenant, so that fiduciary clients do not jump to a new version unplanned.
A banner in the app, you decide when
Instead of forced cloud updates, a banner appears in the ewws Mac app. You look at the changes, plan a time and install with one click. During the payroll week, the banner stays visible until you are ready.
SHA-256 verified, signed
Every DMG download is checked via SHA-256 against the manifest. Tampered builds are not installed. The signed Mac app build carries the Apple Developer ID, Gatekeeper accepts the app without a system override.
Apple stack. Swift, SwiftUI, Liquid Glass
ewws Mac and ewws iOS are built natively in the Apple stack itself. Not ported, not emulated.
The Mac and iOS app are consistently implemented in Swift and SwiftUI, with Apple Liquid Glass design, the Apple Human Interface Guidelines, NavigationSplitView, SF Symbols, Materials and SwiftUI Charts. The same backend (ewws server) serves the native Windows app and the Apple-native variant over the same HTTP API.
Swift and SwiftUI as the mandatory language
ewws Mac and ewws iOS are written entirely in Swift, no Java bridge, no embedded web view. This makes the app as fast and reactive as Mail, Notes or Finder, and respects the platform characteristics instead of hiding them.
Liquid Glass and the Apple HIG at 100%
Materials, toolbar, NavigationSplitView, Form, List and Settings follow the Apple Human Interface Guidelines exactly. Liquid Glass as Apple system material is used throughout. Mac and iPad feel like system apps, not like ported third-party software.
SwiftUI Charts and SF Symbols
Analytics, forecast and management KPIs use SwiftUI Charts instead of purchased chart libraries. Symbols come from SF Symbols and thus match the system font and Dynamic Type. This saves memory, keeps the app light and makes it accessibility-friendly.
A shared Swift package for Mac and iOS
ewws Mac and ewws iOS share a common Swift package with domain, application and infrastructure layer (Clean, Hexagon, DDD). Domain and application logic are written once and executed identically on both Apple platforms.
Operating model by choice
Self-hosted or public cloud. ewws can do cloud, but does not have to.
The operating model belongs to you, not to the vendor. Two paths, one product. A switch stays possible.
Self-hosted
Your own server, your own network, full control. For companies with a clear IT line or sensitive industries where data must not leave the house.
Public cloud
Your own cloud account at a hyperscaler of your choice. Cost model, region and data protection situation stay under your control. ewws does not lock you in.
Approach to AI
AI that strengthens the user and keeps the handling of data controllable.
In ewws, AI is a tool in the workflow. Every suggestion stays traceable, every action under your control, and the model choice stays open.
In the context of work
AI functions work directly in the ERP data, for example with customers, documents and postings. Additional parallel worlds and unnecessary data copies are avoided.
Transparent and auditable
AI suggestions are guided so that context and the relevant basis stay traceable. What the model saw and suggested should stay documented and verifiable in the audit log.
Sovereign model choice
Local models, European providers or completely switched off: you decide which model accesses which data. The AI path is configurable, not predetermined.
Human leads, AI amplifies
AI speeds up routine and gives suggestions. Approvals, postings and deliveries stay in human hands, no automation without confirmation.
ewws versus a typical cloud ERP
The same feature set, a fundamentally different foundation.
Many ERPs for SMEs are browser applications in the vendor cloud. ewws delivers the same commercial feature set, but you keep data, operation and speed. A factual comparison of the category, not of a single product.
ewws
- Data on your server or in your own cloud account, you decide
- Native apps in Swift and WinUI 3, full keyboard and multi-window operation
- AI computes on your hardware, no data outflow to third-party providers
- Eight mandatory Swiss standards at the core of every edition, at no surcharge
- PostgreSQL and open formats, data exportable at any time
- No framework ballast, a hexagonal architecture, maintainable for 20 years
Typical cloud ERP
- Data necessarily lives in the vendor cloud, often outside your control
- Operation in a browser tab, bound to the limits of a web page
- AI functions send documents to third-party cloud services
- Swiss standards often as paid modules or add-ons
- Proprietary data storage, export only limited or for a fee
- A grown framework stack, updates become a constant topic
Our standard
Why ewws takes a clear position in this field.
Many ERP offerings today lead customers into a single operating model. ewws relies on an architecture that leaves you the choice and at the same time stays manageable. This keeps the product predictable years from now too.