Skip to main content
LogLife runs as two independent pieces: a Next.js website hosted on Vercel (marketing site + dashboard) and an OpenClaw plugin that serves session data from your server. The dashboard talks to the plugin through a secure API — your server address and key never reach the browser.

​
Architecture

The website is a static marketing site for most visitors. When a logged-in user opens the dashboard, the Next.js API route proxies requests to the OpenClaw plugin. The plugin reads sessions.json and returns session data. Authentication uses a shared Bearer token — the key lives in your server’s OpenClaw config and in Vercel’s environment variables, never in client-side code.

​
Get started

Follow these guides in order to go from zero to a running LogLife instance:
1

Install the plugin

Clone the repos, build OpenClaw, install the LogLife plugin, and start the gateway.Plugin installation guide →
2

Configure everything

Set up environment variables, plugin config, and Vercel deployment settings.Configuration guide →
3

Set up networking

Put Caddy in front of the gateway for HTTPS, DNS, and access control.Networking guide →

Architecture

Multi-user isolation, generated configuration, and memory layers.

Development

Local development workflow and CI/CD pipelines.

Security

Authentication, phone verification, and data flow.

API reference

Plugin HTTP endpoints documentation.