Deploy Ocular on your own server.

Ocular is a self-hosted budget and finance app with dashboards, charts, multi-year tracking, imports, and authentication. This template runs the official container image, which bundles the static UI (Caddy) and the Genesis API backend, with persistent data under /data/genesis.

Deploy Ocular View source

Your infrastructureAutomatic HTTPSNo lock-in

Screenshots

A closer look at Ocular.

Setup time

A few minutes

Deployment

Your own server

Services

1 connected service

Why Ocular

Everything you need, running where you choose.

Get the full Ocular experience with Easypanel handling the repetitive infrastructure work around it.

Multi-year budgets

Track and carry budgets across years with flexible financial calendars.

Import and export

Bring data from common formats and export your work as JSON.

Genesis backend

API and authentication via the bundled Genesis server (JWT configurable).

Budget clarity

Dashboards and analytics help you understand spending and plans over time.

Self-hosted

Keep financial data on infrastructure you control.

Official image

Uses the published GHCR image maintained by the project.

How it works

From template to live app in three steps.

Easypanel turns the template into real services, storage, and domains on the server you already control.

Already have Easypanel? Open your dashboard at the URL or IP of your own installation.

Installation guide

Open your dashboard

Visit the URL or IP of your Easypanel installation and choose the target project.

Choose Ocular

Open Templates, select Ocular, then review its service names and configuration.

Deploy and open your app

Easypanel starts every service and provisions an HTTPS domain for you.

Installation options

The template asks for these values before creating your services.

Option	Default	Required
App Service Name	ocular	Required
Ocular Image	ghcr.io/simonwep/ocular:v2.3.0	Required
JWT token expiration (ms)	Set during install	Optional
Allow JWT cookie over HTTP (not recommended behind HTTPS)	false	Optional
Initial users (Genesis format) Comma-separated list of username!:password entries. Leave empty to create a single admin user with a random password.	—	Optional

Before you deploy

After deploy, open your domain and sign in using the initial user from GENESIS_CREATE_USERS (default is admin with a random password set at deploy time; copy it from the service environment if you did not set your own value). Use HTTPS in production; only enable HTTP cookies if you access the app without TLS. Change GENESIS_JWT_SECRET only if you understand that existing sessions will be invalidated.

Resources

Project documentation and source code.