Secure member platform

One clean place for your private services.

ToastyHub is a public-facing company website with a protected customer workspace behind sign-in. Sessions stay server-side, provider access stays in the backend, and every signed-in user only sees their own data.

Cloudflare-native delivery Authentik single sign-on Server-managed integrations
Built for small to mid-sized deployments

Simple operations, strict boundaries.

ToastyHub combines a conventional landing page with a secure dashboard for internal and customer-facing data. Authentik handles identity, Cloudflare handles delivery, and the backend enforces every access decision.

HttpOnly Session cookies only, no tokens in browser storage
Per user Server-side filtering for dashboard data and actions
OIDC + PKCE Authentik login with validated state, nonce, and redirect URIs
Backend only Immich and Plex are resolved centrally, not from browser JavaScript
Platform

A normal public website outside, a protected workspace inside.

The public homepage is intentionally simple and accessible. Sensitive account data, provider lookups, and user actions live behind authenticated routes and are enforced on the server.

Public homepage

Use the root route as a clean company front door with clear sign-in and dashboard entry points.

Protected dashboard

Every dashboard route is backed by session checks and per-user filtering before data leaves the backend.

Extendable integrations

Add new providers through server-side adapters without changing the security model in the browser.

Security

Security decisions happen on the server.

ToastyHub is designed to minimize browser exposure. Frontend code renders data and submits requests, but session validation, authorization, claim mapping, provider credentials, and data access checks remain in backend functions only.

Session-first auth

Authorization Code Flow with PKCE, HttpOnly cookies, CSRF validation, and session rotation controls.

Minimal claims

Only the required claims from Authentik are mapped locally: subject, email, display name, and groups.

Least data exposure

Provider tokens stay backend-only, and the dashboard receives sanitized summaries instead of raw API payloads.

Operations

Easy to run, easy to extend.

The stack stays pragmatic: Cloudflare Pages, Pages Functions, D1, Authentik, and small adapter modules for services such as Immich and Plex.

Identity via Authentik OIDC login stays centralized and users are mapped locally by validated claims.
Private data in D1 Users, sessions, and integration snapshots are scoped per account and queried server-side.
Adapter-based growth Immich and Plex are already backend-managed, and more providers can follow the same pattern.
Start secure

Keep the browser simple. Keep the backend in control.

Use ToastyHub for a polished public presence and a secure private workspace without exposing sensitive provider credentials or security-critical logic to the frontend.