Gablura helps teams turn scattered tasks into clear priorities, protect deep work time, and maintain steady progress — without the complexity that slows everyone down.
Why Gablura Exists
Scattered tasks. Siloed projects. Endless context-switching. Productivity tools promised to fix these problems but instead became part of them. Gablura was built from scratch to address this — a focused, opinionated platform that helps teams see what matters, work on it without interruption, and track meaningful progress.
Most teams don't fail because they lack tools — they fail because their tools add noise instead of removing it. Gablura is built around the principle that every feature must reduce cognitive load, not add to it.
Shallow busyness is the enemy of meaningful progress. Gablura ships with built-in Focus Sessions (Pomodoro, deep work, custom) so your team can carve out uninterrupted time in a world of constant pings.
Not solo todo lists. Gablura is workspace-first — with role-based access, real-time collaboration via SSE, team analytics, and activity feeds that keep everyone aligned without micromanagement.
What Gablura Ships
8 core feature areas, 119 custom hooks, and a fully typed API layer.
Full-featured task lifecycle from creation to completion — with subtasks, dependencies, recurring schedules, priorities, and bulk operations.
Switch between List, Kanban Board, Calendar, and Daily Tasks — each optimised for a different planning style with drag-and-drop support.
Built-in Pomodoro, deep work, and custom focus modes with time tracking and productivity analytics. Protect uninterrupted work time.
Comments, @mentions, team notifications, and an activity feed — all delivered instantly via Server-Sent Events without page refreshes.
Workspace dashboards with task completion rates, focus session stats, team activity tracking, capacity visualisation, and custom charts.
Cloudinary-backed file uploads and attachments with a built-in browser UI, storage usage tracking, and optimisation tools.
Stripe-powered plan management with billing history, invoices, usage-aware plan limits, and subscription status tracking.
Owner, Admin, and Member roles with workspace-scoped data isolation. RS256 JWT auth, Argon2 hashing, HTTP-only cookies, and audit logging.
Under the Hood
Every technology was chosen deliberately — not for hype, but for correctness, performance, and maintainability.
App Router — SSR, RSC, API routes
UI library with concurrent features
Strict type safety across the codebase
Utility-first styling — v4 engine
Animations and page transitions
Icon system across all UI
Server state, caching, optimistic updates
Built-in client state for theme & auth
HTTP client with interceptors + JWT attach
Performant, uncontrolled form handling
Runtime schema validation
Analytics charts and data visualisations
Session management + Google OAuth
Token auth issued by backend on exchange
Token revocation, rate limiting, caching
Hosting, CDN edge network, preview deploys
File uploads, storage, media optimisation
Backend database with ORM and migrations
How It's Built
Three-Layer Architecture
Frontend Layer
Next.js 16 + React 19 + TypeScript + Tailwind v4
Backend API Layer
Express.js + Node.js + Prisma ORM
Data Layer
PostgreSQL + Prisma + Upstash Redis
Request Lifecycle (e.g. Create Task)
User triggers action (e.g. Create Task)
Custom hook fires — optimistic update applied
Axios POST with RS256 JWT attached
Backend validates token → checks RBAC → writes DB
SSE notifies assignees in real-time
TanStack Query cache updated — UI reflects truth
Real-Time via SSE
No WebSocket overhead
Each authenticated user holds a persistent GET /api/v1/notifications/stream connection. The backend pushes events in real-time — no polling, no WebSocket infrastructure required.
Auth Token Flow
The Person Behind It
Gablura was designed and built entirely by Mohammad Raihan Gazi — from the database schema and RS256 JWT auth system through to the Kanban board drag-and-drop (coming...), Pomodoro focus engine, and Paddle billing integration.
The goal was never to ship a side project — it was to build a production-grade SaaS platform from scratch and learn every layer of the stack deeply. Gablura v1.1.0 Stable shipped on August 11, 2026.

Mohammad Raihan Gazi
Creator & Maintainer · Gablura
409+
Commits
119
Custom Hooks
99.9%
TypeScript
Repository Languages
Engineering Principles
These are not aspirations — they are verifiable properties of the Gablura codebase.
RS256 JWT auth, Argon2id password hashing, HTTP-only cookies, CORS enforcement, rate limiting, timing-safe comparisons, and workspace-scoped data isolation. Security isn't a feature — it's the baseline.
Server Components minimise client JS. TanStack Query deduplicates requests and applies optimistic updates. Vercel Edge Network delivers assets globally. Speed is a design constraint, not an afterthought.
119 custom hooks encapsulate all data-fetching and side-effect logic. Components are thin. Business logic is reusable. The codebase is structured to be extended, not rewritten.
TypeScript in strict mode across 98.5% of the codebase. Zod schemas validate all runtime inputs. API responses are fully typed end-to-end. If it compiles, it's correct by construction.
Vitest for unit tests, Playwright for E2E. Custom hooks are isolated and testable. The architecture separates concerns so that every layer can be verified independently.
Server-Sent Events deliver notifications instantly without WebSocket infrastructure overhead. The useNotifications hook handles reconnection, backoff, and cache invalidation transparently.
Open Contribution
Gablura is source-available under a custom license. We welcome contributions, bug reports, and feature discussions across both the client and the backend API.
How to Contribute
Fork the repo
01Fork gaziraihan1/gablura-client on GitHub and clone your fork locally.
git clone https://github.com/gaziraihan1/gablura-client.gitBranch from dev
02Active development happens on the dev branch — always branch from it and open pull requests against it.
git checkout -b feature/your-feature-name devSet up locally
03Install dependencies, create .env.local from the example, and run the dev server (the backend API runs on :5000).
npm install && cp .env.example .env.local && npm run devTest & lint
04Run the quality gates before pushing: ESLint, the Vitest suite (with MSW-mocked API), and the TypeScript typecheck.
npm run lint && npm run test:run && npx tsc --noEmitOpen a Pull Request
05Push your branch to your fork, then open a PR against dev — describe what changed, how you tested it, and add screenshots for UI work.
git push origin feature/your-feature-nameDocumentation & Resources
ARCHITECTURE.md
System design decisions, data flow, and design patterns.
CONTRIBUTING.md
Full guidelines for the client: setup, test conventions, and review process.
Backend Repository
The Express + Node.js + Prisma API powering Gablura.
Backend CONTRIBUTING.md
Backend contribution guide — module architecture, cron jobs, and testing.
CODE_OF_CONDUCT.md
Our community standards for respectful collaboration.
Security vulnerabilities should never be reported as public GitHub issues. Email focurabusiness@gmail.com for responsible disclosure.
Start a free workspace on Gablura today. No credit card required. Full feature access from day one.