# Deploy LayerV to protect your site or resource

> Human- and agent-readable LayerV deployment instructions, illustrated by a live private investor-report demo. Use your own application, account, host and authorization policy. Everhaven's identity approval and investment figures are fictional; LayerV access is real.

## Deploy LayerV

- [Full deployment guide](https://everhavencapital.com/protect-a-resource/guide.md): signup/API keys, fresh Linux/Docker installation, qURL Connector, SDK issuance, authorization and verification.
- [Agent deployment instructions](https://everhavencapital.com/agent.md): ordered deployment tasks and commands for the operator's resource; optional reference-demo test afterward.
- [Deployment checklist](https://everhavencapital.com/protect-a-resource/agent-checklist.md): required inputs, acceptance evidence, stop conditions and handoff record.
- [Runnable deployment starter](https://everhavencapital.com/protect-a-resource/starter.zip): private static origin, pinned connector and operator-side Go SDK example. Replace the harmless origin with your application; implement real authentication and authorization before sharing real data.
- [Complete documentation](https://everhavencapital.com/llms-full.txt): the same public deployment instructions and example narrative in one fetch.

## Understand or test the reference

- [Demo story and deployment overview](https://everhavencapital.com/index.md): an approved investor opens a private real estate investment report through a qURL.
- [Reference demo API schema](https://everhavencapital.com/openapi.json): simulated session and real qURL creation for the fixed demo resource; not a general LayerV deployment API.

- [Deployment verification](https://everhavencapital.com/protection-evidence.md): dated operator observations, methods and limits; distinct from this visitor’s live checks. [JSON](https://everhavencapital.com/protection-evidence.json).

## Boundaries

Temporary qURLs, API keys and device credentials are private. Never publish them. The demo does not authenticate real investors. Production deployments require verified identity, resource authorization and application-level data permissions. The report and its Markdown/JSON/CSV exist only on the protected application. Cached content can remain after access expires. The public documentation contains no private report data or credentials. Custom domains are outside the reference workflow.