Build with Presence
Your product.
A more personal check.
Bring Presence into the experience your customers already use. In software, at a physical checkpoint or within a service—make the person part of the action.
Where does your
product meet a person?
Choose a moment. Explore how Presence could fit inside your customer experience.
Integration opportunities. Interfaces, physical checks and operating requirements are agreed and validated for each deployment.
Your experience.
A shared verification step.
Keep the product’s purpose and authority clear. Presence supplies a check; your system decides what that evidence allows.
Your interface names the action and the person it needs.
Connect the person.The verification step supplies evidence for that request.
Your service enforces its permissions and carries out the action.
What remains yours
Your customer relationship, accounts, permissions, transaction rules and execution controls. Together we define the customer-facing confirmation, supported interfaces and responsibility for each failure or recovery path.
Software & platforms
A familiar check inside a digital journey.
Add the verification step where your product needs it: at sign-in, a sensitive account change or an approval. Keep your application’s own customer experience, permissions and business logic.
- Map the request and return to the right screen.
- Keep authorisation and enforcement on your server.
- Design refusal, expiry and recovery as part of the journey.
Integration scope
The platform publishes OIDC sign-in guidance, Auth.js examples and a management API. Physical checks and action-specific approval integrations are scoped separately.
Devices & access systems
Connect the physical checkpoint to your product.
For access-control providers, equipment makers and device manufacturers: define where the person presents their Key and how the result reaches your controller or service.
- Agree the checkpoint, interface and response time.
- Plan enclosure, installation, power and servicing.
- Keep safety controls and emergency access independent.
Integration scope
Hardware integration is a joint engineering scope. Reader design, sensing, installation and the full operating environment require validation; a standard embedded module is not being offered here.
Services & customer journeys
Bring the person into the moment that matters.
For a payment, rental, collection or protected service, place the check inside the existing journey. Connect it to the right request while your business retains the customer relationship and the final decision.
- Define the confirmation and what it means.
- Connect to existing accounts, entitlements and support.
- Measure completion, exceptions and operating cost.
Integration scope
Eligibility, regulated identity checks and payment processing remain with the responsible providers. Branding, delivery model and commercial terms are agreed for the integration.
From your product
to a working integration.
- 01
Map the journey.
Name the user, the action and the step that needs a check.
- 02
Connect the systems.
Agree interfaces, responsibilities, branding and recovery.
- 03
Validate together.
Test one bounded workflow before agreeing the path to scale.
A place for
your engineering team.
The public integration guide covers website sign-in, company directories and the management API. It provides a concrete starting point for a technical conversation.
Available references and validation
OIDC website sign-in, Auth.js guidance and SCIM provisioning are documented. A software connection does not establish physical Key performance or certify a customer deployment. Hardware, product approval flows and deployment suitability need their own evaluation.
Partnerships
You bring the product.
We build the connection.
Work with 4SI at the level that fits your business.
Technology partners
Integrate the verification step into software, devices or services.
Discuss product integrationIndustry partners
Bring domain expertise and a use case worth developing together.
Shape an industry applicationWhen the physical product itself needs verification
Presence Layer is a separate direction for connecting an item to its identity, origin or custody. If your question concerns the object as well as the person, include it in the integration discussion.
Explore Presence LayerWant to use Presence in your own organisation?
You do not need to become a technology partner to discuss an application.
Talk to sales