Your data. Your operating model.
Use familiar PostgreSQL operations to keep shared memory available and recoverable.
Back up the database
Palace Server persists memory in your PostgreSQL database with pgvector. Standard PostgreSQL backup tooling, including pg_dump, applies. Include your organization’s retention policy, recovery objectives, and restore testing in the deployment plan.
Keep database backups separate from the host they protect, and test a restore against an isolated database with the required extension and a compatible service version before relying on it.
Keep configuration recoverable
Protect the deployment configuration, license, and signing secrets through your organization’s secret-management process. Database encryption at rest comes from your database and storage setup. Configure verified TLS for database connections with sslmode=verify-full.
Watch readiness and usage
Use /healthz and /readyz for health and readiness checks. Logs go to standard output. Prometheus metrics are available at /metrics; restrict that endpoint at your proxy.
Plan license renewal
The server verifies its signed license locally. Online revalidation is optional and disabled by default, so an offline deployment needs a process for replacing expiring licenses. A running server keeps working for a default 14-day grace period after expiry; an expired key prevents a new startup.
Monthly plans need online revalidation switched on (PALACE_LICENSE_API_URL): a monthly license lasts about 35 days and is rolled forward automatically while the subscription is active. Annual licenses cover the whole paid year, so annual plans can run fully offline.