Skip to content

Technical data

Technology by company size.

Staffing agencies decide on their IT by the size of the business: one workstation, one office, one server, several branches. This page is structured exactly that way — for each scenario, a typical classic desktop installation compared with EagleDesk.

Comparison values: illustrative, generalised information on classic desktop installations — no connection to other vendors.

Scenario

Single workstation

Founders, sole traders, small branch offices

No longer needed
  • SQL instance
  • Office licence
  • Backup routine
Scenario 1: Single workstation — Classic desktop installation / EagleDesk
Aspect Classic desktop installation EagleDesk
Workstation Windows PC; minimum hardware depends on the software Any device with a current browser — Windows, macOS, Linux, tablet
Database Local SQL database on the same PC — raises the need for processing power and memory Operated in an EU data centre, nothing to install
Interface & licences Office/database licences, to be procured by the customer Browser interface, no Office licence needed
Screen Often a fixed minimum resolution for desktop screens Responsive from smartphone to large display
Backups not specified Daily, integrity-checked, keys stored separately

Scenario

Up to 5 workstations in the office

Typical agency with dispatch and accounting

No longer needed
  • “Server PC”
  • Licences per seat
  • Update appointments
Scenario 2: Up to 5 workstations in the office — Classic desktop installation / EagleDesk
Aspect Classic desktop installation EagleDesk
Workstations Windows PC per seat; one computer often also carries the database All seats equal in the browser — no PC has to “play server”
Database SQL database on the office network Operated centrally, tenant data field-encrypted
Interface & licences Office/database licences on every workstation No Office licences, users managed through roles
Printing Printer set-up per workstation (drivers, paper trays) PDF output with stored branding — prints on any printer
Maintenance & updates not specified Automatic, without installation on the workstations

Scenario

More than 5 workstations

Growing businesses with their own IT support

No longer needed
  • Windows Server
  • SQL full version
  • Hardware cycle
Scenario 3: More than 5 workstations — Classic desktop installation / EagleDesk
Aspect Classic desktop installation EagleDesk
Server Own Windows server, sized by the number of users No server on the customer side — operated by the provider in the EU
Database SQL database, a licensed full version depending on size Included, with backup and monitoring
Interface & licences Office/database licences per workstation Browser; no licence per workstation — billing is by active workers
Permissions not specified Roles, individual permissions and data access per user
Security not specified Field-level encryption, 2FA, audit log, enforced HTTPS

Scenario

Several branches & teleworking

Branch networks, home office, dispatch on the road

No longer needed
  • Remote Desktop
  • Terminal server
  • VPN access
Scenario 4: Several branches & teleworking — Classic desktop installation / EagleDesk
Aspect Classic desktop installation EagleDesk
Remote access Usually via Remote Desktop to the central server Directly in the browser, encrypted via HTTPS — no VPN, no Remote Desktop
Mobile use not specified Tablet and smartphone; Employee Web App and customer portal on the home screen
Locations Branches often on a shared terminal server Locations and cost centres per branch with a location filter; data access per user
Operation & backups Central server in your own office — operation and backups are your responsibility No server in the office: operated in a data centre with daily backups and health check; external mirroring of the backups is being prepared

Illustrative, generalised information on classic desktop installations; no connection to other vendors. Actual requirements depend on the specific software. “not specified” means there is usually no requirement for this — the responsibility lies with the customer.

Data import and migration in six steps →

Data sheet

EagleDesk in detail

System requirements

Browser
Current versions of Chrome, Edge, Firefox or Safari
Devices
PC, Mac, Linux, tablet, smartphone — from 375 px width
Installation
None. Employee Web App and customer portal optionally on the home screen
Office
Not required — documents are produced as PDF
Printing
Any printer that can print PDF
Internet
A regular broadband or mobile connection

Hosting & operation

Location
Data centre in Germany (EU)
Operation
By the provider — no server on the customer side
Backups
Daily, integrity-checked; keys stored separately
Monitoring
Health-check endpoint for external uptime monitoring
Tenant separation
Dedicated derived key per organisation

Security & GDPR

Transport
HTTPS/TLS enforced, encrypted sessions
Storage
Field-level encryption of sensitive data, encrypted documents
Sign-in
Two-factor via app (TOTP) in the office and in the Employee Web App, password change on first login
Traceability
Audit log; sensitive fields such as name, social-security number, IBAN or findings not in plaintext
Data-subject rights
Access under Art. 15 (employees, applicants, customer contacts) with the details required by Art. 15(1), automatic erasure periods under Art. 17 — for employees from the deletion date entered
Record
Record of processing under Art. 30 from the system

Interfaces

Accounting
BMD/DATEV-ready journal-entry CSV per invoice or as a monthly batch export with a run number, with receivable and revenue accounts per tax case and a check report
E-invoice
ebInterface XML (the Austrian standard); per customer also ebInterface 6.1, PEPPOL BIS 3.0 or XRechnung with a check before sending — for download or attached to the invoice e-mail
SFTP
Journal-entry CSV and e-invoice (with Premium All In also the cost-accounting file) optionally via SFTP to a server of your choice, with a mandatory server fingerprint
Import
Clients, contacts and open assignments via CSV — with a dry run and a per-row error list; employees via CSV import with an error message per row
Bank reconciliation
Import bank statements as camt.053 or CSV and match payments to invoices (suggestions, you confirm)
API
REST API v1 with a token per application, individually chosen scopes (read access; customer hours can also be submitted), optional IP restriction and an OpenAPI description; webhooks with signature, retries and a delivery log
Archive
DMS export via WebDAV or REST In development

Updates & support

Updates
Automatic, with no installation on your side; rare maintenance windows are announced in the system in advance
Year-end changeover
Tariffs and parameters versioned — new values apply from the effective date
Support
By ticket right in the application, by email and phone — directly from the developer

Open beta · Since 19 October 2026

Ready to plug in?

The open beta with real customers has been running since 19 October 2026. Talk to us: we show you the system in an online demo and, if you wish, set up your trial account after the conversation.