One register of your people and every system they sign into. When someone leaves, one action closes it all.
None of them arrives as a single invoice. That is exactly why they go unnoticed.
Every hire and every leaver is a manual round: create, grant, remember, revoke. The register lives in a spreadsheet, the passwords live in chat. It is not a one-off cost. It drips every week.
A leaked password and a fired employee work equally well from anywhere on earth. How many people left you last year, and are you certain every door behind them is shut?
When was this person created? Who opened that credential, and from what address? When the question comes from an auditor or a client, the answer has to be excavated by hand across several systems.
One portal, and each of them sees their own part of it: exactly as much as their role allows.
“Who has access to what” stops being a question you ask one person’s memory. A leaver is one action, not a three-day thread. And when an auditor or a client asks, the answer exists without excavating five systems by hand.
Rights are cut at the server, not in the interface. A hidden button is not security. Sign-in is bound to a machine and a network, passwords sit encrypted, every action lands in the log. It installs on your server, and nothing leaves it but three licence fields.
Joining and leaving stop being a lap around the chats. One card per person shows what they were given and by whom. The person opens their own work systems without asking a colleague for the password.
Not hidden buttons in a UI. Refusals happen at the API; the interface only reflects a decision the server has already made.
An employee enters their ID and a six-digit code their own computer generated locally, like the one ticking at the top of this page. The first machine binds to the person automatically on first sign-in; a second one is refused until IT releases it. There is nothing to phish and nothing to forward in a chat.
Three methods, chosen per role: the machine-bound agent, a standard authenticator app, or IT approval with a PIN. The binding survives a browser reinstall.
A role builder: section, object, action and scope (own, own team, everyone). Press a role and watch what is left of the same table:
A closed field disappears from the table, the filters, the search and the API response. It is not hidden with CSS. A record outside your scope answers 404, not 403: a role that may not see a person must not learn that the person exists.
Office networks are set as IP ranges, a role can be marked office-only, and an individual can be given an exception with an expiry date. Sections such as the credential vault, exports, backups and the audit log can be sealed to the office network for everyone, administrators included. A welded door is welded for everybody.
34 automated checks cover the firewall decision matrix: deny precedence, malformed ranges, IPv6, client-address spoofing, behaviour when the database is down.
Someone leaves on a Friday evening. One action instead of a memory-driven tour of eight systems:
Everything that happened sits in the log with the name of whoever did it: 120 event types in five categories, filters by date, role and person, and a timeline for one employee. Personal data inside the log stays masked for anyone not cleared to see it.
Editions
The core is the same for everyone. Your edition comes with your licence and sets the structure, the words on the screen and the roles and fields offered at setup. You tick what you need; nothing else is created.
| Edition | The person | Larger unit | Smaller unit |
|---|---|---|---|
| Trading & Call Center | Agent | Brand | Desk |
| Company | Employee | Office, department | Sub-department |
| Retail Chain, on request | Staff | Region | Store |
Trading & Call Center and Company ship ready today. Retail Chain is set up on request: store staff stay records without sign-in, managers and head office sign in, and the shared access of each store is kept with the store. , the floor map on its own for offices with shifts and dense seating, is in early access.
Fewer than 30 people and no IT person? A team password manager and changing shared passwords on the day someone leaves cover most of it. Want a hosted version for small teams? Tell us.
Everyone runs the same build. What you licence appears under Administration → Modules with a switch; what you have not licensed simply is not there. No locked menus, no upsell banners. Adding a module is a licence change on our side, with no reinstall and no downtime.
Modules add to any tier. From 101 people Multi-office and CSV import are included. Prices on the main page.
Or we do it for you. Installation, access policies tuned to your structure, migration of your current spreadsheets, and ongoing operation. Updates land when it suits you: nobody pushes anything to you overnight.
A flat licence per instance, priced by size, not per seat; yearly, or monthly at the yearly price ÷ 10. Hiring inside your size does not move the invoice. Outgrow it and you get 10% extra room, at least 5 people, for 30 days to move up. Tiers, modules and managed operation are on the main page.
One at a time, seven in total. Nothing is sent anywhere and nothing is stored. If everything is in order, that is what it will say.
Short answer on the right. Tap a row for the detail.
Connectors
When someone leaves, Wardyn does not only lock its own doors. A connector disables the account in the system itself (mail, directory, ERP, CRM, the badge system on your office doors) and writes down what it closed.
We build the connector for your system as part of onboarding: 1C, Logo, your CRM, your door access control, or any system with an admin API. Scope and timing are agreed with you before the licence starts.
With access control connected, the badge stops opening the office door the moment the person leaves.
What your IT and your auditor will ask, answered with how it actually works.
People, roles, credentials and the log live in your database. Three values reach us: the licence key, your domain and the number of people.
Stored credentials are encrypted with AES-256-GCM. The key lives in your server's environment; we never hold it.
People sign in with an ID and a code from their own computer that lives 15 seconds. A new computer waits until IT approves it.
Every request is checked against the role on the server. The interface only reflects a decision already made.
A role can be office-only, a person can get a dated exception, sensitive sections can be sealed to the office network.
Showing a stored password is logged with the person, the IP and the country, and capped at 20 an hour.
120 kinds of action, filters, a timeline per person, export to a file, kept up to 24 months.
If our licence server is unreachable, your portal keeps full access for 7 days. An ended licence turns read-only; nothing is deleted.
You decide when to update. Updates from inside the portal, signed, with a restore point and automatic rollback, arrive with the next release.NEXT RELEASE
Wardyn Agent shows the code and opens systems. No agent service, no driver. On office machines an optional script records the serial number for the binding.
Where Wardyn stops today, so you do not find out in month three.
We will show it on a real instance: a machine-bound sign-in, permissions cutting, a refused login from outside the office, and an offboarding with its log entry. Then a 14-day pilot on your own server. When it ends the portal turns read-only, and nothing is deleted.
Who sits where, which machine is on which desk, and what to close when someone leaves. Inside Wardyn as a module, or on its own for offices with shifts and dense seating.
Three things the map keeps in one place, so nobody has to reconcile a seating chart, an asset list and an access list by hand.
Switched on under Administration → Modules, on top of any tier. The map uses the same people, roles and audit log as the rest of the portal, so a leaver disappears from their seat the moment access is closed.
€690 a year per instance
The same portal with only the floor map switched on, for offices that need seating, shifts and machines but already run sign-in elsewhere. Upgrading to full Wardyn later is a licence change, nothing to migrate.
€1,290 a year up to 100 seats, €490 for every further 100
Early access: it runs on a live instance, and we show its current state on the call before you buy.
A photo or a sketch is enough. In twenty minutes we draw part of it, seat two shifts and show how machines stay with their desks.
Wardyn