Skip to content
WebsitePanelStatus
NolayDocumentation
WebsitePanelStatus
SectionsConcepts: What is stored where
Getting started
  • Section overview
  • What is Nolay
  • What is a VPS
  • Server requirements
  • Connecting a server
  • First project
Guides
  • Section overview
  • Domains and HTTPS
  • Secrets
  • Tunnel behind NAT
Concepts
  • Section overview
  • What is stored where
Reference
  • Section overview
  • Error codes
  • nolay.toml
Security
  • Section overview
Migration
  • Section overview
Troubleshooting
  • Section overview
Changelog
  • Section overview
Getting started
  • Section overview
  • What is Nolay
  • What is a VPS
  • Server requirements
  • Connecting a server
  • First project
Guides
  • Section overview
  • Domains and HTTPS
  • Secrets
  • Tunnel behind NAT
Concepts
  • Section overview
  • What is stored where
Reference
  • Section overview
  • Error codes
  • nolay.toml
Security
  • Section overview
Migration
  • Section overview
Troubleshooting
  • Section overview
Changelog
  • Section overview
  1. Documentation
  2. Concepts
  3. What is stored where

What is stored where

Which data Nolay keeps, which stays only on your server and what support can see.

Markdown

The main rule: code, data and secret values live on your server and in your storage. Nolay keeps only settings and the service information the panel needs to show the state.

In short

DataWhere it livesAt Nolay
Source codeon the server, in /var/lib/nolay during the buildno
Container imagesin Docker on the serverno
Project data (volumes, databases)on the serverno
Secret valueson the server, encryptedno, only key names
Backupsin your S3 storageno, the S3 keys are yours too
Application logson the server, streamed to the panel on requestno, the panel does not keep them
Account, organization, rolesin the panel databaseyes
Project settings and version historyin the panel databaseyes
Events, metrics, action login the panel and hub databasesyes

Panel

Keeps the account, organization, servers and projects with their settings, version history, events and server metrics. Secrets are kept only as names and a fingerprint of the set. A code archive streams through the panel and is not saved.

Hub

Keeps the list of agents and their tokens, the command queue until delivery, events and metrics. An archive uploaded through the panel stays on the hub for no more than 15 minutes, until the agent takes it. Secret values in the command queue are encrypted.

Your server

PathWhat is there
/etc/nolay/agent.tomlthe agent config
/etc/nolay/agent.tokenthe connection token
/etc/nolay/agent.keythe secrets encryption key, not included in backups and never sent to the hub
/var/lib/nolaythe agent database (SQLite), build sources, repository cache
/var/lib/nolay/caddyproxy certificates and state

A copy of the agent database does not reveal secrets without agent.key.

What support can see

Support sees what the panel keeps: server and project names, settings, statuses and events. Nolay has no access to the server: the agent has a closed list of commands, and an arbitrary command cannot be run on the server through Nolay. Secret values and database contents are not available to support because Nolay does not have them.

Check it yourself

# the agent listens on no inbound ports
ss -tulpn
# the agent does not run as root
ps -o user,pid,cmd -C nolay-agent
# the status shows only secret names
sudo nolay-agent status

Next

Security: the trust model and the agent's rights.

PreviousConceptsNextReference

On this page

  • In short
  • Panel
  • Hub
  • Your server
  • What support can see
  • Check it yourself
  • Next
Updated 2026-09-23
Nolay

Nolay documentation: connecting your own server, deploys, domains, secrets.

Documentation

Getting startedReferenceChangelogllms.txt for AI

Product

WebsitePanelStatus
Nolay