Your business application, live fast.

Application base, integration and operations already stand as the foundation — all that gets added is your business application. That is why things move fast here and still hold.
You pay for your business logic — not for infrastructure that already exists with us.
The CDS platform — application base, integration and operations

The foundation — the CDS platform

Every business application needs three things: something it uses, something it connects to, and something it runs on. Together these are the CDS platform — in place before your domain logic begins.

Application base

What every application uses — ready, instead of built per project.

  • Cockpit

    One navigation, one dashboard, driven by the user's role.

  • IAM

    Your customers manage their own users. Permissions settled from day one, DSG-compliant.

  • Messaging

    The delivery path for every application: email, SMS and push with templates. Every user decides what they are told about.

Integration

Connected, not bolted on — your existing systems are part of the foundation.

  • Enterprise connectors

    SAP, HubSpot, Salesforce, Microsoft Dynamics and others via REST and webhooks.

  • Data where it is needed

    The connection is a property of the platform, not a project of its own.

  • SAP
  • HubSpot
  • Salesforce
  • Microsoft Dynamics
  • Bexio

Operations

It runs — operated in Switzerland, without you building a team for it.

  • Hosting in Switzerland

    Operated in Swiss data centres — your data stays in the country.

  • Separate environments

    Production and test separated from day one — no weeks until the first test environment.

  • Monitoring and backup

    We notice faults before your users do. Backups run daily.

What runs on the foundation

Business modules that already exist. They are built, in use, and combine with your own domain logic — instead of starting from scratch every time.

  • CPQ — configure quotes

    A selection of services becomes a quote with correct prices. With a playground and over 50 examples to try out.

    To the CPQ module
  • Invoices — make billing transparent

    Customers see their invoices straight from your ERP system, filter them and download PDFs. Fewer support requests.

    To the Invoices module
  • Messages — handle enquiries instead of hunting for them

    An inbox for the exchange with your customers: subject, attachments, history. Every enquiry has an owner and a status.

    To the Messages module
  • Analytics — make the numbers visible

    Visualise key figures, build reports, base decisions on data rather than guesswork.

    To the Analytics module
  • Appointments — book online

    Online appointment booking with calendar integration, automatic reminders and a CRM connection.

    To the Appointments module

The modules come together in the cockpit — one application, one navigation, permissions from the IAM. Your users experience one system, not four bought-in tools.

Your look, all the way through

Your logo and your colours carry through every module, the cockpit, the notification emails and into the documents your customers receive. Possible because every module is built from the same building blocks.

  • Your logo & your colours
  • Cockpit
  • Modules
  • Emails
  • Documents

That is exactly where assembled solutions give themselves away: the application looks like you — but the quote arrives as a PDF in the vendor's layout, and the email right along with it. Not here.

The engineering view

One shared base, integration and operations layer that every business application is built against — instead of one per project. If you know WorkOS: a comparable idea, one level closer to the business domain and cut for business applications. React on the frontend, Spring Boot on the backend, containerised with Docker, orchestrated via Kubernetes. Our AppShell orchestrates the micro-frontends at runtime and provides the cockpit — a standalone business application ships the same way. AppShell, webbloqs and Magellan are open in the CDS technology stack.

Security and operations in Switzerland

Security isn't a pillar of its own here, it's a property of all three. What follows is checkable — not «enterprise grade» as a label, but properties you can hold us to.

Encrypted data transmission
Communication between your users and the platform is encrypted end to end.
Tenant separation
In a multi-tenant environment, each customer's data is strictly separated: their own groups and permissions, automatically limiting access to their own data.
Daily backup
Your data is backed up every day. What you can lose is at most one day — not months of your work.
Your identity provider, not ours
Your users sign in with the identity they already have. For the Wasserversorgung Zürich customer portal that is the City of Zurich's «Mein Konto» — no second password, no user administration nobody wants to maintain.How that works at Wasserversorgung Zürich

This doesn't run in theory

2.5 million people use software from Quatico — roughly one in three people in Switzerland. At Helsana, the City of Zurich, ewz, EKZ, BFH and the Tenants' Association. These applications run on the very foundation that would carry your business application too — see all references.

Let's talk about your business application

Tell us what your application has to do. We will show which parts the foundation already brings and what gets built on top.
Ralph

Let's talk about your platform

Ralph — For questions about the CDS platform and how it carries your business application, talk to us directly.