SaaS and On-Premise

In the European cloud. Or on your own infrastructure.

attendo almost always runs as SaaS: we operate it on Kubernetes in AWS, OVHcloud or Google Cloud, always in a European region. If your data cannot leave your network, we deploy it on-premise as a project.

Talk to an engineer Compare the two options

SaaS in a European region
On-premise as a project
Source code is never handed over

SaaS By default

Kubernetes on AWS, OVHcloud or Google Cloud
Always in a European region
One instance and one database per customer
We run it: backups and updates

On-premise As a project

On your organization’s servers
Database, attachments and backups on your network
Encrypted code and verified boot
No attendo access to your systems

The two options

What changes and what does not

It is the same attendo. What changes is where it runs and who operates the infrastructure.

SaaS and on-premise compared
	SaaS	On-premise (as a project)
Where it runs	On Kubernetes in AWS, OVHcloud or Google Cloud, in a European region	On your organization’s infrastructure, on servers with confidential computing
Who operates the infrastructure	attendo	Your IT team; attendo maintains the software
Database	One per customer, managed by attendo	Yours, managed by your team
Attachments	Managed storage or your own S3	Your S3-compatible or local storage
Backups	Daily, managed by attendo, with an optional copy to your S3	With the policy and destination your team decides
Updates	Continuous, with no downtime on your side	Signed releases; your team decides when they are applied
Source code	Not handed over	Not handed over: it runs encrypted
attendo access to your systems	Not needed: we operate the service	None: no SSH or VPN, outbound connections only
License	Service subscription	Renewable license

By default

SaaS: we run it, in Europe

Your instance (application, database, queues and storage) runs on Kubernetes in AWS, OVHcloud or Google Cloud, always in a European region. We operate it: your team only needs a browser or the app.

Data hosted in the European Union, in a database of your own
Continuous updates, with nothing to install and no work stoppage
Daily backups with verified restores, and a scheduled copy to your own S3 if you want one
Full export of your data whenever you want

See how we protect data

As a project

On-premise: your data on your infrastructure, the software protected

With attendo Private, the on-premise option, the platform runs inside your infrastructure. The database, attachments and backups stay under your team’s control, and attendo gets no access to your systems.

The software ships encrypted and signed: no source code and no repository are handed over. It is a project with your IT team: before go-live, we review the hardware, the network and the integrations together.

On-premise

Six pieces that make it work

Your data never leaves your network

The database, message queue, attachments (on S3-compatible or local storage) and backups live on your infrastructure, next to your corporate systems.
Code encrypted even while it runs

attendo runs in a confidential virtual machine, on servers with AMD SEV-SNP or Intel TDX. The code is only decrypted inside that environment: neither administrators nor the hypervisor see it in the clear.
Verified boot

Before it starts, the machine proves it is an authorized environment, running a valid, unmodified release. Only then does it receive, temporarily, the key that unlocks the application.
Signed updates

New releases arrive signed and encrypted, with no repository access. Your team decides when they are applied and, if an update fails, it rolls back to the previous release.
No access to your systems

attendo needs no SSH, VPN or hypervisor access. Verification, licensing and updates use encrypted outbound connections only (HTTPS).
Operations without a console

Service status, health checks, version, license and connectivity, ready for your monitoring tools. Day-to-day operation does not require logging into the system.

Verified boot

How attendo starts on your infrastructure

The key that unlocks the application does not live on your server: it is handed over each time the machine proves it is what it claims to be.

Step 1
The machine presents its proof

The virtual machine generates a cryptographic proof of its environment: hardware, boot chain and image.
Step 2
attendo checks it

The attendo key service verifies that the environment is confidential, the release is authorized and not revoked, and the installation belongs to your organization.
Step 3
The key is released temporarily

Only then is the key that unlocks the application released. Master keys stay protected outside your infrastructure, in a key management service.
Step 4
attendo starts with your data

The application connects to your database and your systems, which have never left your network.

Licensing

A renewable license that never looks at your data

The installation renews its license on its own, over an outbound connection. If the connection drops, it keeps working for a grace period, and the administrator is warned before any restriction.

Checking the license does not query your database: only technical data about the installation, the release and the environment verification is exchanged.

Requirements

What your infrastructure needs

Infrastructure requirements for on-premise
Piece	What is required
Server	Physical, with AMD EPYC (SEV-SNP) or Intel Xeon (TDX)
Virtualization	Linux with KVM/QEMU and libvirt
Data	Database, message queue, S3-compatible storage and backups, managed by your team
Network	Outbound HTTPS to attendo for verification, licensing and updates
External services	Anything that uses outside services (email, WhatsApp, AI) or is used from outside (mobile app, customer portal) needs your network to allow it. We cover it in the project.

attendo keeps a list of supported hardware, firmware and hypervisors for each release.

When to choose on-premise

Is on-premise right for you?

SaaS is the default and the simplest option. On-premise makes sense if your organization needs any of these:

Strict data sovereignty or residency
The database inside your corporate network
No third-party administrative access to your infrastructure
Integration with internal systems that are not exposed to the internet
Security or procurement requirements that rule out SaaS

What we do not publish

The details, on a technical call

We do not publish the internal architecture, the full list of supported hardware or the details of the key service. If your IT team needs them to evaluate attendo, we share them on a technical call, under a non-disclosure agreement.

The rest of the platform

And when you need it, the rest is already here

Frequently asked questions

What is the default option?

SaaS: we run it on Kubernetes in AWS, OVHcloud or Google Cloud, always in a European region. On-premise is done as a project, when a requirement calls for it.

Can I choose the cloud provider?

It is always a European region of AWS, OVHcloud or Google Cloud. If your organization prefers one, tell us when you request a quote.

Do we get the source code?

No, in neither option. On-premise, attendo ships as a protected machine with encrypted, signed releases; the repository stays with us.

Can attendo get into our servers?

No. On-premise needs no SSH, VPN or hypervisor access. There are only outbound connections for verification, licensing and updates.

What happens if the internet connection goes down?

The license has a grace period: attendo keeps working and the administrator is warned before any restriction. The length is set in the contract.

What if the attendo key service does not respond?

An installation that is already running keeps working. A fresh start needs to repeat the verification, which is why the key service runs in high availability.

Can we decide when it is updated?

Yes. On-premise, your team approves each release before it is applied. With SaaS, updates are continuous and need no downtime.

Does any server work?

No. It needs hardware with confidential computing (AMD SEV-SNP or Intel TDX) and a hypervisor supported by the attendo release being installed.

How much does on-premise cost?

It depends on the project: infrastructure, integrations and license. We do not publish prices: we send you a firm proposal after looking at your case. What the price depends on.

Cookie settings