What has been verified
Built against the provider’s documented API and working end to end, but not yet validated in a live installation.
Boris asks Akiles for access on the doors mapped to the booked resource and hands the customer a magic link or a PIN valid for that booking only.
Beta Built against the provider’s documented API and working end to end, but not yet validated in a live installation.
Built against the provider’s documented API and working end to end, but not yet validated in a live installation.
Requires an active provider account, credentials and any plan required by the provider.
The workflow and limitations documented on this page are the supported scope; validate it with test data before production.
A link or a PIN is enough, which matters for one-off meeting-room guests.
Access begins and ends with the reservation, including when it is cancelled.
Grants, retries and revocations are traceable back to the reservation that produced them.
Add your Akiles credentials in Integrations.
Map Akiles gadgets and doors to your resources.
Boris issues the link or PIN when the booking is confirmed and withdraws it when it ends.
Yes, where the door supports it; the choice is per door mapping.
Built against the documented Akiles API and working end to end in simulation; not yet validated in a live installation.
Create a workspace, add your resources and connect the tools you already pay for. No credit card required.
Create your workspace