London-led technology · Hong Kong company platform · Fukuoka field deployment

Operating infrastructure for controlled real-world environments.

Uriyel connects place strategy, guest access, site delivery, stay readiness and portfolio governance — creating one legible record across people, places, evidence and decisions.

Operator state Live
Applied layers05
Live paths04
Operating regions03

Product architecture

One technology brand. Five connected operating layers.

Each layer addresses a distinct real-world problem while sharing the same evidence spine, permission logic and client-facing reporting structure.

01

Core

Governance, portfolio memory and decision control.

For founders, owners and operating teams that need one durable record across people, places, permissions, risks and outcomes.

  • Decision, authority and responsibility registers
  • Cross-layer risks, priorities and reporting
  • Portfolio continuity beyond individual projects
02

DestinationWorks

Destination strategy, partner mapping and place-readiness.

For destination operators, venue groups and place-based programmes testing a market, building an audience or coordinating regional partners.

  • Site, market and seasonal operating intelligence
  • Venue, supplier and stakeholder relationship maps
  • Guest journey, readiness and deployment briefs
03

AccessOS

Premium access, guest flow and partner utility.

For private events, memberships, VIP tiers and invitation-led environments where access must remain selective and provable.

  • Digital passes and scan-ready verification
  • Guest tiers, permissions and arrival records
  • Partner benefits, redemption and continuity
04

SiteWorks

Project visibility, attendance and site-control records.

For property works and controlled project teams that need clearer evidence, safer access flows and owner-visible reporting.

  • Check-in, check-out and attendance records
  • Risk acknowledgement, site notes and photo logs
  • Owner-side dashboards and exportable reporting
05

StayWorks

Guest-readiness, turnovers and owner reporting.

For short-stay properties, serviced apartments, boutique hotels and overseas-owned accommodation.

  • Guest-ready checks and cleaner sign-off
  • Turnover evidence, access notes and room issues
  • Owner-facing summaries across property portfolios
Coreholds
DestinationWorksframes
AccessOSadmits
SiteWorksdelivers
StayWorksmaintains

Playable operating demo

One system logic. Five operating contexts.

Select a layer and watch the record move. The interface changes by use case; the underlying pattern remains evidence, ownership and visible decisions.

Core

Brief opened

Step 1 of 5

The deployment objective, operating environment, owners and constraints are captured in one controlled brief.

Brief → authority → decision → governance

Positioning

One evidence spine behind the visible experience.

Uriyel is not a disconnected stack of ticketing, construction and hotel tools. It is a private operating infrastructure layer for owners, founders and teams whose public experience depends on controlled work behind the scenes.

Core carries governance. DestinationWorks frames the place. AccessOS controls admission. SiteWorks records delivery. StayWorks maintains readiness. Each deployment can begin with one layer and expand without losing its operating memory.

Operating geography

A distributed structure with distinct functions.

Uriyel is being shaped across three connected locations rather than forcing every function into one city.

01

London

Command and relationships.

Product direction, client development, institutional access and capital-facing work.
02

Hong Kong

Company and APAC platform.

Corporate base, regional partnerships and market-development infrastructure.
03

Fukuoka

Field deployment and depth.

Destination, cultural, property and hospitality environments tested in place.

Pilot model

Start with one controlled deployment.

Uriyel can begin through Core, DestinationWorks, AccessOS, SiteWorks, StayWorks or a combined operating layer where governance, access, delivery and reporting overlap.

01

Pilot

For one controlled deployment, site, destination or property.

  • Scoped setup
  • Basic operator console
  • Initial evidence and reporting flow
02

Operating

For active teams and recurring operations.

  • Controlled roles and decision records
  • Client-facing updates
  • One or more applied layers
03

Portfolio

For multi-site, destination or owner-side environments.

  • Cross-layer governance
  • Partner and owner reporting
  • Private operational design

Enquiries

Discuss a deployment.

For Core, DestinationWorks, AccessOS, SiteWorks, StayWorks or a combined operating layer, use the form or email L. S. Severus & Co.