Skip to content

For large organisations

One platform for people, sites and the working day.

Run time and attendance, shift schedules, leave, access control, fleet tracking and payroll inputs across many sites in Cyprus. Give each team the view and permissions it needs.

  • Many sites and departments
  • Terminal and mobile clock-ins
  • Approved hours for payroll

The working picture

Connect the records your teams use every day.

A clock-in is the starting point. Managers can review exceptions, approve time and prepare the records that payroll needs, alongside schedules, leave, doors and vehicles.

  • People and time

    Plan shifts, record attendance, review missing or unusual punches and approve hours.

  • Sites and access

    Use terminals for attendance and, where installed, control which people can enter each door.

  • Fleet and field work

    View vehicle trips and location data beside the working day of field teams.

  • Payroll inputs

    Export approved time and overtime for payroll review. Payroll calculation is a separate process.

For IT and operations

Architecture and integration details.

The platform combines a Vue 3 web client, a .NET 8 ABP application and PostgreSQL. This is how the platform works today.

  • Multi-tenancy and isolation

    ABP tenant context and tenant IDs separate workspace records. Organisation scope grants limit the sites and departments a user can see.

  • Identity and authorisation

    OpenIddict handles OAuth2 tokens. Role permissions and site and department grants control access. Bring your SSO provider to the integration review so federation requirements can be assessed.

  • Live events

    Attendance updates use server-sent events (SSE) to push changes to the portal, without a periodic refresh loop for that stream.

  • Terminal edge

    The terminal edge uses a Layer 4 proxy with health checks and active and standby gateway routing where a standby is configured. The platform backfills records held by the standby after failback.

  • Store and forward

    Terminals retain punches through a connection break and send them when they reconnect. The phone app persists its offline punch queue in encrypted private storage and retries transport failures.

  • Release engineering

    A release takes a database snapshot before migration, switches the release symlink, checks health and automatically restores the previous release when the new API fails to come up. Database changes are not reversed automatically; the snapshot allows a manual restore.

  • Observability

    Serilog application logs, gateway records and health checks give operators evidence for diagnosis and release decisions.

  • Security and privacy

    Permission checks, scoped reads and per-client edge rate limits protect access. Audit records capture selected changes. GDPR handling and retention are set out in the data processing terms.

  • Integrations and APIs

    REST endpoints serve the portal and integrations. Sofia HR Hub exchange and approved-hours CSV export support payroll handoff. CyCom delivery is available as a project once the interface is agreed. Other ERP mappings need a defined project scope.

  • Data residency

    The production origin is hosted on Hetzner infrastructure in Finland, in the EU. Cloudflare provides a global edge, so this is not an EU-only processing claim.

Built for many sites and teams

A structure for many people and many sites.

Tenant boundaries, site and department grants, dedicated terminal gateways and streamed attendance changes keep the work organised as an estate grows. Capacity is sized and checked for each rollout.

  • One organisation, many views

    A manager can work within granted sites or departments while administrators retain the wider organisation view.

  • Devices outside the web request path

    Gateways accept terminal traffic and the application ingests their records, so device connections have their own layer.

  • Changes pushed to viewers

    The live attendance stream sends updates to connected viewers instead of making every screen ask repeatedly for changes.

Availability

Keep clock-ins safe through short interruptions.

A web release briefly restarts the API. The continuity design protects clock-ins taken while the server or network cannot be reached; it does not promise an uninterrupted web session.

  • At the terminal

    The terminal stores each scan and sends it when the connection returns.

  • On the phone

    The app keeps an encrypted offline queue and retries when transport is available. Rejected punches stay visible for review rather than becoming an accepted clock-in.

  • At the site and edge

    A configured standby terminal gateway supports failover. An optional on-site Offline Hub can keep a site operating on its own and forward records later.

  • During a release

    The deploy checks the new API and automatically rolls the application back to the previous release if it fails health checks.

Continuity depends on the device and site setup. Capacity, recovery steps and SSO requirements should be checked in the rollout design.

Map the platform to your estate.

Tell us about your sites, users, identity provider, terminals and payroll or ERP interfaces. We will review the integration and continuity design with your IT team.

Talk to our team