Today view
See the current class, what is next, and how the rest of the day is laid out.
Blockly OSS gives the same product language to self-hosted users.
The open-source branch keeps Blockly focused on schedules, tasks, and day planning while leaving deployment, data ownership, and infrastructure in your hands.
Deployment model
Self-hosted Next.js app with Supabase-backed data and auth
Target setup
One deployment per student or operator-controlled instance
Brand relationship
Same Blockly brand, wordmarks, and interaction language as the hosted product
Core product features
Blockly OSS keeps the product centered on a schedule-first student workflow instead of a broad, decorative dashboard.
Week and calendar views
Handle rotations, holidays, and one-off overrides without needing a separate schedule system.
Task manager
Create and track class-linked tasks with due dates and clear overdue states.
Reminder support
Notification timing can be tuned for the same school-day cadence used in the hosted version.
Preset schedule templates
Start from common school schedule structures and edit from there instead of building everything from zero.
Operator control
Hosting, retention, and deployment choices stay with the operator rather than a managed cloud service.
Reference architecture
The reference stack is intentionally direct: frontend app, Supabase client access, and isolated student data.
App layer
- Next.js frontend
- PWA-capable browser experience
- Local preference storage where appropriate
Data layer
- Supabase Auth and PostgreSQL
- Row Level Security on primary tables
- Per-user data isolation by design
Quick setup
Bring your own Supabase project and move from clone to working app with a short configuration path.
Install dependencies
Clone the repository and install packages with a current Node.js environment.
Configure Supabase
Create a project, run the setup SQL, and add the public URL and anon key to environment variables.
Run locally
Start the app, sign in, and optionally load demo data to validate the initial setup.
Environment variables
- NEXT_PUBLIC_SUPABASE_URL
- NEXT_PUBLIC_SUPABASE_ANON_KEY
- NEXT_PUBLIC_SUPABASE_AUTH_PROVIDERS (optional)
Deployment options
- Vercel
- Netlify
- Cloudflare
- Self-hosted Next.js environments
Security model
- Supabase Auth for identity
- RLS and FORCE RLS on primary data tables
- No service role key in client code
- Ownership checks across related tables
Prefer the hosted version?
Blockly Hosted and Blockly OSS share the same brand system. If you want the managed product instead of running your own deployment, request hosted access.