SaaS
A dedicated URLab environment.
URLab operates the platform within the contractual and security framework agreed with your organisation.
- Dedicated environment and access
- Provisioned compute and storage resources
- Platform supervision by URLab
Start and deploy
A pilot on real work. Then a controlled path to scale.
URLab is an enterprise platform. The starting point is not a generic subscription, but an actuarial use case concrete enough to measure execution, control, and value.
Adoption journey
From the first engagement to a durable capability.
Each stage supports an explicit decision on business value, operational control, target architecture, and the conditions for broader adoption.
01
Before the pilot
Scope
We select representative work, define the expected output, and identify the controls that must remain with your experts.
- Use case, data, and scope
- Success criteria and measurement protocol
- Roles, approvals, and security constraints
02
Three months
Pilot
Your actuaries perform the engagement with URLab, observe agent execution, and assess the results in real working conditions.
- Dedicated environment and actuarial support
- Execution of complete studies or processes
- Measurement of time, quality, and control
03
After validation
Enterprise deployment
The platform expands to selected teams, methods, and processes through the deployment and governance model suited to your organization.
- SaaS or BYOC deployment
- Integration with identity, data, and controls
- Codification and rollout of approved methods
Target architecture
A deployment suited to your data and controls.
Hosting, connections and responsibilities are validated during the pilot. Exact mechanisms depend on the selected architecture and are not assumed before scoping.
BYOC
The platform in your cloud.
Deployment sits within your cloud environment when sovereignty or integration constraints require it.
- Data retained within the agreed boundary
- Integration with your identities and networks
- Explicit allocation of operating responsibilities
Interfaces are defined before wider rollout.
The pilot confirms authorised systems, data flows, calculation environments and operating controls.
Data and storage
Sources, volumes, formats, access rights and retention rules.
Identity and access
Users, roles, authentication and segregation of responsibilities.
Runtimes and tools
Authorised Python, R, SQL, notebooks, engines and libraries.
Outputs and downstream processes
Reports, files, APIs or target databases and their approvals.
Responsibilities
Operating ownership is defined before production.
Security, operations, data, models and actuarial decisions do not have the same owner. The allocation is adapted to the selected deployment model.
Your organisation
- Owner of data and subject-matter methods
- Approval of users, access and authorised use
- Actuarial decisions and sign-off
URLab
- Agreed platform and software components
- Support and supervision under the contract
- Technical traceability available within scope
Shared framework
- Architecture, integration and change management
- Incidents, escalation and continuity
- Criteria for moving from pilot to scale
Security, availability, support and reversibility commitments are those in the contract and approved architecture; this page creates no additional commitment.