Turn identity governance questions into clear next steps.
Explore Seafront IGA pilots to assess your priorities, uncover improvement opportunities, and make informed decisions before committing to a broader deployment.
The 48-hour delivery window starts once the agreed data, access and preparation are ready.
AI Capability Pilot · Video hosted on YouTube.
Choose the question you want to answer.
AI Capability Pilot
“How can AI help configure our identity governance?”
Turn selected roles, access needs and approval flows into an AI-generated draft IGA configuration. Explore the result with test data in a Seafront test environment.
Key outputs
A model of your selected IGA use cases.
An AI-generated draft configuration in the agreed test environment.
Lifecycle Savings Pilot
“What could we automate and what could it save?”
Use your HR and directory data to simulate lifecycle changes and estimate the potential value of automation, without writing changes to production.
Key outputs
Proposed account and group changes.
Licence-reclaim opportunities and an illustrative savings estimate.
NIS2 & DORA Access Pilots
“Where are the gaps in our access management?”
Review current accounts and access to identify issues such as active leaver accounts, unclear ownership and access that needs review.
Key outputs
Prioritised findings and account-level lists.
Access-review material and practical recommendations linked to relevant IAM requirements.
What happens in each pilot?
Preparation for the Lifecycle Savings, NIS2 and DORA pilots includes a signed NDA, data processing terms and an HR CSV export. Seafront uses read-only access to one directory, either Active Directory or Microsoft Entra ID. The 48-hour delivery window starts once preparation is complete. The results walkthrough takes place at the end of that window.
AI is used only in the AI Capability Pilot. The Lifecycle Savings, NIS2 and DORA pilots work with your supplied data and do not require AI.
See how AI can help turn your selected IGA requirements into a draft configuration. The pilot gives you a concrete result to review in a Seafront test environment and a basis for deciding how to take the configuration further.
What we work with
Selected user roles and access needs.
Approval flows.
Target systems represented with placeholders and test users.
What happens
Model the selected use cases.
Use AI to generate a draft configuration.
Export the configuration, add the agreed organisation details and import it into the agreed Seafront test environment.
Exporting the configuration, adding organisation details and importing it do not themselves require AI.
Where compatible, you can also use your own trusted AI tool to connect to your Seafront environment through the Seafront MCP server.
What you receive
A model of the selected roles, access needs and approval flows.
An AI-generated draft configuration imported into the agreed Seafront test environment.
Agreed next steps for taking the configuration further.
What the pilot will show
See how the AI-generated draft configuration reflects your selected roles, access needs and approval flows. Explore those scenarios with test data in the agreed Seafront test environment.
Scope: This pilot uses test data. It does not include production-ready configuration, production integrations or processing of real data by AI. The test setup and access are agreed with you. Continued access and independent testing after the pilot are agreed separately.
See what changes Seafront would propose from your HR and directory data, and estimate the potential value of automating recurring identity tasks.
What the pilot will show
See which account and access changes Seafront would make for joiners, movers and leavers across your organisation, and what those changes could save annually.
What we work with
Provide an HR export covering the last 12 months of joiners, movers and leavers, plus annual account and access ticket volumes, average handling times, licence prices and the groups that assign licences. Name one IT and one HR contact who can answer questions during the pilot. Where ticket figures are missing, agreed estimates are identified in the business case.
What happens
Compare current directory attributes with values calculated from the agreed rules.
Simulate joiner, mover and leaver changes.
Explore selected access requests and pilot-team approvals.
Include an external consultant scenario.
Produce reporting and a sample group access review.
After the pilot, you’ll have
An annual savings estimate based on your HR history, ticket volumes and licence prices.
A list of simulated account and group membership changes.
Proposed access rules by job, unit and contract type, with an estimate of how much current access they would cover.
A list of accounts with potential for licence reclamation.
Results review and next steps
The walkthrough covers the simulated scenarios, reporting, a sample access review and the savings estimate. It includes a proposed rollout plan from simulation to live provisioning, starting with a pilot group.
Scope: The pilot is read-only. It does not provision changes to production or include a live HR integration or connections to other applications. Continued access to the pilot environment and independent testing are agreed separately.
What could lifecycle automation save?
Adjust the example assumptions to explore potential annual time savings and value.
Example: an organisation of approximately 1,000 people, including employees and external users.
Annual volumes include employees and external users. The same time, cost, productivity and licence assumptions are applied to both.
IT time saved
847 hours / year
IT time value
€46,585 / year
Licence value
€4,900 / year
New-hire productivity value
€52,500 / year
Combined illustrative annual value (potential)
€103,985
An illustrative estimate based on your assumptions, not guaranteed cash savings or net ROI. Check for overlap between categories. Licence value depends on subscription terms and whether licences can be reduced or reused. Seafront subscription, implementation and operating costs are not deducted.
Build a current-state view of identity and access issues relevant to the IAM part of NIS2.
What the pilot will show
Identify active accounts belonging to leavers, accounts without a known owner, privileged accounts without a known owner, and external accounts missing a sponsor or end date in the data reviewed.
What we work with
Provide an HR export that includes end dates for people who left in the past 12 months. Identify privileged groups and admin roles, explain how external accounts are identified in your directory and share an external-user register if available. Name a contact who can answer questions during the pilot.
Review areas
Active accounts belonging to leavers.
Account ownership.
External-user sponsors and end dates.
Privileged accounts and group memberships.
Dormant accounts older than 90 days, where the necessary activity data is available.
Identity-data quality.
After the pilot, you’ll have
A risk-ranked report linking access-control findings to relevant NIS2 requirements.
Account-level CSV appendices and a register of external accounts and guests identified in the available data.
A draft of 5–10 candidate access roles based on current group memberships.
Results review and next steps
The walkthrough reviews the findings by risk and outlines next steps for managing leaver accounts and running regular access reviews.
Scope: This is a read-only current-state assessment. It does not implement or test automated lifecycle or approval workflows. It supports the IAM part of NIS2. This pilot provides IAM findings and recommendations. It is not a regulatory compliance check or certification.
Build a current-state view of accounts and access for the critical or important systems you select.
What the pilot will show
See who can reach the selected systems through the groups in scope. Identify active leaver accounts, accounts without a known owner, privileged accounts without a known owner, and external accounts missing a sponsor or end date.
What we work with
Provide an HR export that includes end dates for people who left in the past 12 months. Identify privileged groups and admin roles, explain how external accounts are identified and share an external-user register if available. List the systems that support your critical or important functions and the groups that grant access to them. Name a contact who can answer questions during the pilot.
Review areas
Account ownership and active leaver accounts.
Privileged access.
Access groups associated with the selected systems.
External-user and service-provider sponsors and end dates.
An access baseline for review.
After the pilot, you’ll have
A risk-ranked report linking access-control findings to relevant DORA requirements.
Account-level CSV appendices and a register of external accounts and guests identified in the available data.
A draft of 5–10 candidate access roles based on current group memberships.
A baseline for reviewing access to the selected systems.
Results review and next steps
The walkthrough reviews the findings by risk and outlines next steps for managing leaver accounts and running regular access reviews.
Scope: This is a read-only assessment of the agreed identity and access scope. It does not implement production provisioning or approval workflows. This pilot provides IAM findings and recommendations. It is not a regulatory compliance check or certification.
Let’s define your next step.
We’ll agree on the question to answer, the pilot scope, the preparation needed and what you will receive.