kenoplug/keno-vault

Purpose and Entry Points

Keno Vault is a static, browser-based personal net-worth tracker with free/pro feature gating. The primary user entry is index.html; authenticated dashboard and settings views are under pages/dashboard.html and pages/settings.html. Vercel serves the frontend and routes serverless endpoints via vercel.json and server.js.

Frontend Application Shell

The vanilla JavaScript client owns UI rendering, authentication state, asset CRUD, dashboard KPIs, charts, history, exports, and plan-aware feature access. js/app.js is the central application coordinator, with finance computations separated into js/calculators.js. Shared deployment, Supabase, admin, and site constants are configured in js/config.js.

Paths:

• index.html

• js/app.js

• js/config.js

Dashboard and Financial Intelligence

Dashboard presentation is split from the core client behavior: pages/dashboard.html supplies the dashboard view and css/dashboard.css provides dedicated styling. Financial modeling—including retirement, debt, allocation, depreciation, tax, and net-worth-related calculations—is concentrated in js/calculators.js, allowing UI flows to consume computed results rather than embed formulas.

Paths:

• pages/dashboard.html

• css/dashboard.css

• js/calculators.js

Identity, Data, and Authorization Boundary

Supabase provides Google authentication, PostgreSQL persistence, synchronization, and row-level security. supabase-migration.sql defines the backend schema/policies, while the browser uses the configured public Supabase credentials. The frontend should remain limited to user-scoped operations protected by RLS; privileged subscription updates and account deletion run in Edge Functions.

Paths:

• supabase-migration.sql

• js/config.js

• supabase/functions/delete-account/index.ts

Security and Local Privacy Controls

Sensitive client-side controls—session auto-lock, PIN/privacy behavior, and encrypted backup mechanisms—are organized in js/security.js. Encryption uses the browser Web Crypto API, keeping encryption/decryption in the client boundary rather than requiring a separate cryptographic service.

Paths:

• js/security.js

• js/app.js

• pages/settings.html

Subscription and Payment Flow

A user initiates Pro purchase through a Supabase Edge Function that creates a Bachs checkout. Bachs asynchronously calls the webhook function after payment; that trusted server-side path activates or updates the subscription record. The client then reads subscription state to enforce free limits and unlock Pro modules. Bachs supports cards, bank transfers, mobile money, and crypto.

Paths:

• supabase/functions/create-checkout/index.ts

• supabase/functions/bachs-webhook/index.ts

• supabase-migration.sql

Server-Side Automation and Integrations

Supabase Edge Functions isolate external integrations and privileged actions from the static frontend. ai-advisor provides an AI-backed advisory boundary, while send-notification supports outbound notification workflows. The frontend additionally obtains foreign-exchange data from open.er-api.com; Chart.js renders client-side visualizations.

Paths:

• supabase/functions/ai-advisor/index.ts

• supabase/functions/send-notification/index.ts

• supabase/functions/bachs-webhook/index.ts

Runtime and Deployment

The product is primarily a static HTML/CSS/JavaScript application deployed on Vercel. Supabase hosts auth, database, and Deno/TypeScript Edge Functions; Vercel configuration and the Node server file define deployment/runtime integration points. Tailwind is loaded from CDN, with custom CSS retained for dashboard-specific behavior.

Paths:

• vercel.json

• server.js

• css/dashboard.css