# Invisible to the public. Accessible by invitation. — LayerV demo

Everhaven Capital is a fictional real estate investment company. Maya Chen is an investor in Harbor House, an apartment property. Everhaven wants to share her quarterly report without exposing its report application to the public internet.

In the story, Maya has signed in and is authorized to view this investment. The backend gives her a temporary qURL. LayerV routes her to the private application through its outbound qURL Connector. The origin has no public inbound web port before, during or after her visit.

**This is a LayerV demo: sign-in and approval are simulated; LayerV access is real. The company, property, investor and all figures are fictional.**

## Try the reference demo

1. At https://everhavencapital.com/ select **Create my access link**.
2. Select **Open investor report** within 60 seconds. The qURL is single-use, with up to two minutes of access.
3. The report checks its protected connection on arrival. **Check access now** makes another fresh request. Read the timestamped result in **This visit’s connection checks**.
4. A second fresh check runs 130 seconds after page load. Read its actual result; no expiry status is inferred from a timer. A failure can also indicate a network or service problem. Previously downloaded content can remain visible.
5. Create a fresh qURL and repeat the check to distinguish expiry from an unavailable application.

The report contains property performance, quarterly cash flow, Maya's distribution and a management update. In-page JSON, CSV and Markdown controls fetch data from the protected application. The public site does not host the report.

## Inspect the evidence

The homepage separates [dated deployment verification](https://everhavencapital.com/protection-evidence.md) from this visitor’s checks. The record describes the tested origin boundary, successful qURL access, and post-window behavior, with UTC timestamps and limitations. Machine-readable results: https://everhavencapital.com/protection-evidence.json. These observations do not establish that all host services are invisible or that every attack path was audited.

## Deploy LayerV for your own site or resource

This demonstration is an example of LayerV deployment, not a template requiring an investment business. To protect your own HTTP site, portal, dashboard or service:

1. Sign up at https://layerv.ai/ and create the scoped API keys described in the guide.
2. Install your application and the qURL Connector on Linux with Docker. Keep the application's listener private; publish no inbound application port.
3. Enroll the connector, preserve its device credential and save the actual CRID returned by LayerV.
4. Authenticate callers through your existing identity provider, such as Auth0. On your server, authorize the specific resource before using the LayerV SDK to create a qURL. Keep API keys server-side and retain application-level data permissions.
5. Verify direct isolation, authorized access, separate-caller denial, expiry and restart behavior before adding real data.

Use the complete instructions, commands and acceptance criteria:

- [Deploy LayerV: full Markdown guide](https://everhavencapital.com/protect-a-resource/guide.md)
- [Deploy LayerV: agent instructions](https://everhavencapital.com/agent.md)
- [Agent deployment checklist](https://everhavencapital.com/protect-a-resource/agent-checklist.md)
- [Docker and Go SDK starter](https://everhavencapital.com/protect-a-resource/starter.zip)

A qURL grants temporary resource access; it does not establish investor identity or replace per-investment authorization. LayerV's gateway is distinct from your origin. This reduces direct exposure without guaranteeing an unhackable application or erasing downloaded data. The working demo uses qurl.site; custom domains are outside this walkthrough.