Sign in

Find your organisation

Every organisation has its own Inlinea address. Type the first word of yours, or the whole address, and we will take you there.

Take the tourBook a demo
ZERA by Inlinea

Open the application. Never the network.

ZERA, Zero Endpoint Resource Access: one branded front door to every private application, desktop and SaaS service, opened from any browser with nothing installed and secured by the browser it runs in.

Book a demoTake the ZERA tour
portal.ministry.exampleExample
  • Access verified
  • Browser attested
  • Policy: Finance staff

Swipe to see each example portal.

  • Ministry, in ArabicExample
  • BankExample
  • Service provider's clientExample
  • Access verified
  • Browser attested
  • Policy: Finance staff

What ZERA replaces

Four front doors become one

ZERA can replace the VPN portal, the VDI landing page, the jump host and the intranet app list, at once.

  • VPN portalWhole-network access to reach one application.
  • VDI landing pageA virtual desktop to reach a few applications.
  • Jump hostShared admin paths, and no recordings.
  • Intranet app listLinks with no policy behind them.
One WorkspaceEvery application, desktop and SaaS link, per person, per rule.

The front door

One Workspace for everyone you work with

Employees, contractors, partners and citizen-facing teams open one Workspace: private web applications, remote desktops and servers as Secure Sessions, and bookmarks to SaaS applications, all behind your sign-in and your Access Rules. Each group sees only its own catalogue.

Finance sees six cards.

apps.organisation.example

Make it yours

Your portal, not a vendor's launcher

Studio is a full design workbench for the Workspace: ten presets including the KSA Government standard, a palette builder, live contrast checks, Arabic and English, your own domain. Draft, review, then publish.

Studio: make it yours
StudioReady to publish · lowest text contrast 6.2:1
Preset
Brand colour

Applied exactly as chosen, the way the Colors editor applies it.

Appearance
Language
apps.organisation.exampleLive preview
A sample Workspace re-rendered live from the real Studio presets. The contrast chip runs the same checks Studio runs before publishing: text below 4.5:1 blocks publishing.

Browser security, built in

The browser that opens it is part of the policy

The platform that publishes the portal also secures the browser that opens it: attested browsers admitted server-side, in-page controls for clipboard, print, file transfer, screen capture and watermark, and evidence in the Browser Security Log. It works with the browser people already use, under one policy.

  1. 1BrowserEnrolThe Inlinea extension holds a device key the browser cannot export and enrols the browser. You can require approval first.
  2. 2Inlinea serverAttestSigned heartbeats keep a short-lived attestation alive, valid for 45 seconds by default.
  3. 3ZERA gatewayAdmitThe gateway verifies the attestation locally on every request, with no round trip. No attestation, no page.
  4. 4WorkspaceLockIf the extension disappears, the Workspace locks within about five seconds. Revoking a browser ends its session at once.
Workspace lock
~5 s
After the browser extension disappears.
Attestation window
45 s
Default life of an admitted resource's attestation.
Revocation
At once
Revoking a browser ends its session immediately.
Browser Security: the control matrix, prevention versus containment

Privileged sessions

RDP, SSH, VNC and Telnet, recorded and controlled

Managed credentials injected by the gateway, Session Evidence for every session, clipboard and file transfer enforced before data reaches the browser, idle and maximum durations, and an administrator who can end a live session.

Secure Sessions
finance-desktop.example.com
Ledger
Accounts payable214 items
Approvals waiting12
Last closing30 Sep

Establishing a secure session

Inlinea is verifying your access and connecting you to the resource.

How it reaches your apps

One connector dials out. Nothing opens inbound.

Follow a request through the edge, the ZERA gateway and the encrypted private network to the application, and see which component decides what.

Inlinea server
  1. Browser
  2. Edge
  3. ZERA gateway
  4. Encrypted private network
  5. Connector
  6. Application

Step 1 of 10

The browser resolves the resource's address to your tenant and opens an HTTPS connection.

One connector dials out. Nothing opens inbound at the private site.

Built for compliance programmes

The controls auditors ask for, built in

Every launch, sign-in and session is logged, privileged sessions are recorded, sign-in attempts are limited, access can be limited by country and network, and the whole service runs single-tenant in your country.

  • LogsAudit, Traffic, ZERA Access and Browser Security logs with summaries, export and retention settings.
  • Session EvidencePrivileged sessions recorded on the server and replayed in the Control Center, keystrokes optional.
  • Sign-in protectionAttempt limits and blocked addresses on every Protected Service.
  • Country and network limitsAllow and block lists by country and by address range, per service.
  • Single-tenantYour own environment, never a slice of a shared cluster.
  • In your countryRun in the region you choose, with dedicated environments and on-premises as options.

Frameworks buyers map these controls to

  • NCA ECC
  • PDPL
  • ISO/IEC 27001
  • SOC 2 Type II
  • GDPR

Inlinea's own status for each framework is published in the Trust Center. Compliance status

Delivered as a service

Delivered as a service, wherever you need it

Inlinea runs it: no portal servers, no VPN concentrators and no jump hosts for you to operate. At your private site, one connector, an Inlinea Agent acting as a routing device, dials out.

Global footprint
Dedicated environment available147 cities · 58 countries · 7 areas

Same policy as the Inlinea Agent

The day someone needs the whole network, it is the same identity, the same groups and the same Access Rules.

Inlinea Agent

Questions buyers ask

Does anything install on the user's device?
No. ZERA needs only a browser. Where a resource requires an attested browser, the Inlinea browser extension is needed for it; your administrators deploy it through managed browser policy. The Inlinea Agent is a separate, installed mode for people who need the whole network.
Which browsers work?
Any modern browser opens the Workspace. Browser Security uses the Inlinea extension for Chromium-family browsers, such as Chrome and Edge, and for Firefox, from the browser stores or by managed deployment, and the Inlinea app for Safari.
What does the extension see?
Its policies apply only to the Workspace and to the Protected Resources your organisation marks as extension required. It keeps the browser's attestation alive with signed heartbeats, applies your controls inside those pages and reports evidence to your Browser Security Log. Web Filtering extends category policy to other websites.
Can we use our own domain?
Yes. The Workspace and every Protected Service can sit on your own domain, with certificates issued automatically, wildcard included.
Can the portal be in Arabic?
Yes. Studio supports Arabic and English with a full right-to-left layout, further languages per organisation, a translation for every visible string and a typeface for each script.
Where is our data?
In your own tenant: a single-tenant environment Inlinea runs in the region you choose, a dedicated environment in any of 147 cities, or your own data center. Logs and Session Evidence stay in that tenant.
What happens when a user leaves?
Block them in your identity provider or in Inlinea. Live Sessions signs a person out everywhere in one action: identity sessions, devices, Secure Sessions and browser sessions all end. With Directory Sync from Microsoft Entra ID, a user blocked there is blocked in Inlinea too.

Your secure workspace, in your brand and your language.

Book a demoTake the ZERA tour