Fully Managed Urlaubsverwaltung
as a Service

Deploy Urlaubsverwaltung as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Urlaubsverwaltung is an open-source leave and absence manager built for German and DACH teams. It handles holiday requests, approvals, sick notes, overtime and per-state public holiday calendars. It combines the convenience of a per-seat HR portal with the control of software you host yourself.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

Urlaubsverwaltung

Urlaubsverwaltung

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Urlaubsverwaltung Preview Image

ABOUT THE SOFTWARE

What is Urlaubsverwaltung

Urlaubsverwaltung is an open-source web application for tracking holiday, sick leave and overtime. Employees file requests, managers approve them, and the office keeps the entitlement records. It is built around German leave practice rather than adapted to it.

The project is licensed under Apache 2.0 and maintained by Focus Shift Software GmbH in Karlsruhe. It has been in continuous development for over a decade and carries more than 17,000 commits, with dozens of releases a year rather than one annual drop. Container images are published to both GitHub Container Registry and Docker Hub.

The application is written in Java and runs on Spring Boot with a PostgreSQL database. Two lines are active: 5.x, which still receives patch releases, and 6.x, which arrived with 6.0.0 in June 2026 on Spring Boot 4 and JDK 25. The interface ships in German and English. Public holiday calendars cover many countries and, for Germany, each federal state separately, so a Bavarian site and a Hessian site can share one instance.

FEATURES

What Urlaubsverwaltung does

The application covers the full absence cycle for a German team: request, approval, record, balance. It also carries sick notes, overtime and part-time working models, so the leave file matches what payroll and the personnel officer actually need.

Leave requests and approvals

Employees file a request against their own balance and see it move through approval, rejection or cancellation. Managers act from the same screen they use to review the team.

Two-stage approval

A second approver can be required before a request becomes final. It is how a line lead’s decision still clears the office when a works council plan governs the year.

Role model built for HR

Office, Boss, Department Head and Second Stage Authority are separate roles, and one person can hold several. Inactive keeps a leaver’s history without giving them access.

Sick notes and the AU period

Sick leave is recorded separately from holiday, with the certified incapacity period tracked against it. A sick day inside booked leave does not silently consume entitlement.

Overtime tracking

Overtime balances sit next to leave balances for the same person. An optional companion time-recording application extends this for teams that need clock-level detail.

Public holidays per federal state

Holiday calendars are configured per country and, in Germany, per federal state. Sites in different states share one instance without one office inheriting the other’s holidays.

iCal subscription feeds

Three scopes are published as calendar feeds: your own absences, your department, and the whole company. Any client that reads an iCal URL can subscribe to them.

Departments, overview and API

Departments group people for approval and for the absence overview. An HTTP API at /api exposes the same records for reporting or a payroll handoff.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to Urlaubsverwaltung the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Urlaubsverwaltung

German employers have had a duty to record working time since the Bundesarbeitsgericht decision of 13 September 2022. The statute that fixes the electronic detail is still not passed in 2026, and the April 2025 coalition agreement commits to legislating it. Teams are digitising absence records now.

Running the application is the easy half. The half that consumes evenings is the Java runtime, the database engine, the identity provider and the upgrade path between major versions. Version 5.0.0 changed two of those at once. It removed the LDAP and Active Directory security providers, leaving OpenID Connect as the only way in, and it dropped MariaDB and MySQL in favour of PostgreSQL.

That combination is the operational trap worth knowing about before you self-host. An install still on 4.x cannot jump straight to 5.x. It has to reach the last 4.x release, convert its database to PostgreSQL, and have sign-in rebuilt on an identity provider, all before the first 5.x container will start. Version 6.0.0 then moved the runtime to Spring Boot 4 and JDK 25. Teams that skipped a line find out during the migration, not before it.

Sign-in has its own sharp edges. A self-signed identity provider certificate is rejected until it is added to the Java trust store inside the container, which is documented in project issue 1496. Azure sign-in fails with AADSTS900144 when the authorize request arrives without a scope parameter, per issue 1560. Neither is hard once you have seen it. Both cost a working day the first time.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Urlaubsverwaltung on DANIAN

The same instance serves very different shapes of organisation. What changes between them is the department layout, the identity provider and which holiday calendars are switched on. The price does not change with headcount.

34-PERSON ENGINEERING FIRM

Moving the works council holiday plan off a shared spreadsheet

Departments mirror the two shift groups, second-stage approval is on so the office confirms every line lead decision, and holiday calendars for two federal states run side by side. Sign-in goes through the company Entra ID tenant, on the domain urlaub.[company].de. The office pulls the annual overview once a quarter for the works council meeting.

12-PERSON SOFTWARE AGENCY

Putting absences next to delivery milestones

One department per client pod, with the department iCal feed subscribed into the delivery calendar so project leads see who is away before they commit a date. Sign-in runs through a self-hosted Keycloak, in the region closest to the team. Contractors use the same provider, so directory removal ends leave-record access the same day.

58-STAFF CARE PROVIDER

Keeping ward rosters readable at approval time

Each ward is its own department, so the absence overview loads one roster rather than the whole organisation. Part-time working models are set per person, sick notes are recorded against the certified period, and the operations lead uses terminal access to pull reports. Ward leads see only their own department, which keeps the overview readable mid-shift.

COMPARISON

Four ways to run Urlaubsverwaltung

Leave management is bought per head almost everywhere, so the bill grows as the team does. The three self-run paths flatten the licence cost and move the spend into hardware and hours instead. Here is the arithmetic at three team sizes.

The table prices the parts that appear on an invoice. It does not price the parts that appear on a calendar: the evening a database engine migration runs long, the morning an identity provider certificate expires, the afternoon spent working out why approval mails link to an internal hostname. Those hours are why the middle two rows cost more than they look.

Path5 people10 people25 peopleYour ops timeWho does the upgrades
Per-seat HR SaaSabsence.io absence module, €2 per user per month€10/mo€20/mo€50/moNoneThe vendor. Your records live on their platform.
Self-host on a VPS2 vCPU / 4 GB production-class VPS at about $24/mo, plus object-storage backup and monitoring$44/mo$44/mo$44/mo5–10 hours to set up, then 1–2 hours a monthYou, including the 4.x database and sign-in rebuild.
Home or office serverSynology DS923+ at about €650 over 36 months, power, a business line and an off-site backup target€210–667/mo effective, at any team size2–4 hours a monthYou, plus the hardware when it fails.
DANIAN managed UrlaubsverwaltungOne instance, your region, your domain€9/mo€9/mo€9/moNoneUs, staged on a copy first.

Ops-time cost is real money. At a freelance sysadmin rate of €60–120 an hour, the VPS path adds €60–240 a month in hours on top of the $44 in infrastructure. The per-seat path is the cheapest option below roughly five people, and the most expensive one above ten.

BY INDUSTRY

Urlaubsverwaltung for specific industries

Leave rules are not uniform. A works council, a collective agreement, a rest-period rule or a client billing model each put different demands on the same four screens. These four sectors are where the configuration decisions actually differ.

Works councils hold co-determination rights over holiday principles and the annual holiday plan under Betriebsverfassungsgesetz section 87(1) number 5. We configure departments to mirror your shift groups and switch on second-stage approval, so a line lead decision still clears the office before it becomes final. A press shop leader approves the request, the office checks it against the agreed plan, and the absence overview shows who is already booked that week. Arbeitszeitgesetz section 16(2) requires records of hours worked beyond eight per day to be kept for at least two years, and daily off-site backups cover that window without a separate export job.

Staff on the TVöD collective agreement receive 30 days of annual leave on a five-day week, and that sits alongside Sonderurlaub and state-level Bildungsurlaub entitlements. Urlaubsverwaltung tracks each of those as a separate absence type, so a Bildungsurlaub day does not silently consume the statutory balance. We add the five extra days that SGB IX section 208 grants staff with a recognised severe disability as its own entitlement line. The office maintains entitlements per person, the department head approves, and the annual overview prints the picture a personnel officer needs for the leave file.

Arbeitszeitgesetz section 5 requires an uninterrupted rest period of at least eleven hours after the working day, and staffing floors under the Pflegepersonaluntergrenzen-Verordnung limit how many people can be away at once. We map each ward to its own department so the absence overview loads one roster at a time instead of the whole organisation. Part-time working models are configured per person, which matters when a nurse works three days in one week and four in the next. Leave carried into the following year has to be taken by 31 March under Bundesurlaubsgesetz section 7(3), and the balance view shows that deadline against each person.

Vertrauensarbeitszeit remains permitted under the April 2025 coalition agreement, but the recording duty established by the Bundesarbeitsgericht on 13 September 2022 applies whatever the working model. We set up one department per client pod and hand you the department iCal feed, which subscribes into a delivery calendar so a project manager sees absences next to milestones. Sign-in runs through your existing identity provider, so a contractor leaving the directory loses access to the leave record at the same time. Leave accrued during long-term sickness survives up to fifteen months under settled case law, which matters when a lead developer is out for a quarter.

Bundesurlaubsgesetz section 3 sets the statutory floor at 24 working days on a six-day week and 20 on a five-day week, which matters where staff rotate between the two roster patterns across sites. We give each site its own department so a store or depot manager approves their own people, and we switch on the federal state holiday calendar that site actually sits in. Section 4 grants full entitlement only after six months of employment, so seasonal joiners are tracked against that qualifying period rather than the calendar year. Google ended support for Google Sync on 1 May 2025, so deskless staff subscribe to the department iCal feed from a phone instead of relying on a proprietary sync path.

FAQ

Frequently asked questions

Three groups of questions, in the order people usually ask them. First the technical detail of running this particular application, then what moving an existing install involves, then how billing, support and the platform itself work.

01

Technical and configuration

We run the current stable release and pin it per instance, so an upgrade is a scheduled change rather than a surprise.
It is documented behaviour, not a defect. Urlaubsverwaltung creates the first successfully authenticated user with the Office role, which carries full administrative rights. We coordinate the first sign-in with you so the account that lands the Office role is the one you intended. After that, roles are assigned from inside the application.
Not any more. Two-way sync with Google Calendar and Exchange was marked deprecated in version 4 and removed in version 5. What replaced it is iCal subscription feeds at three scopes: your own absences, your department and the whole company. Any calendar client that reads an iCal URL can subscribe to those.
The feeds are secret-URL links rather than authenticated sessions, so anyone holding a link can read the absences behind it. The company-wide feed only becomes available once someone with the Office role turns it on. We leave that setting off on a new instance and switch it on when you ask. A link can be regenerated if it leaks.
The project publishes no official figure, and a Java application will size its heap to whatever memory it can see. We cap the heap to the container limit rather than the host, which is the difference between a predictable service and an occasional restart under pressure. Leave records are small; the runtime is the part that needs headroom.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes, on every plan. Point a record at the address we give you and the certificate is issued and renewed automatically. We also pin the application URL to that domain, so links inside approval and reminder mails resolve to your host. Getting that setting wrong is a common cause of unusable notification email.
They come from the application itself, per country and per German federal state, so sites in different states can share one instance with different holidays. We set the defaults during onboarding from the locations you give us. Adding a site later is a settings change, not a redeployment.

03

Billing, support and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Urlaubsverwaltung for 7 days

No card. Cancel from the dashboard.