The infrastructure layer
for modern software.
Tuli provides the core systems behind modern applications — identity, data, billing, and domain logic — in one unified platform.
Applications built on Tuli ship production-ready from day one.
🌷 Tuli is running in production — powering Nextbook
In production
Tuli powers Nextbook.
Nextbook is a live learning platform for Norwegian high school students.
Auth, enrollment, progress tracking, content delivery, and subscriptions all run entirely on Tuli.
This is not a prototype.
It is the system behind a real product.
Backend
Go API with modular domain architecture
Database
PostgreSQL with automated schema migrations
Auth
JWT sessions, refresh rotation, provider bridging
SDK
Typed client with methods for every module
Pipeline
Content publishing with atomic operations
Infrastructure
Containerized, multi-environment configuration
System design
Four layers. One platform.
Tuli is structured as a layered system designed for long-term product compounding.
Core
Infrastructure foundation providing database integration, configuration, logging, health monitoring, and HTTP server.
Modules
Self-contained business domains. Each module owns its schema, service logic, and API surface.
SDK
Typed client mirroring every module endpoint. Applications integrate through the SDK, never through direct database access.
Applications
Products built on Tuli inherit the entire stack from day one.
Tuli is not assembled per product.
It compounds.
Engineering
Production characteristics
- Typed SDK surface
- Module isolation by domain
- Event-driven identity lifecycle
- Migration-based schema evolution
- Health-checked deployment pipeline
Platform modules
Production domains. Not plugins.
Every module follows the same internal structure: schema migration, repository layer, service layer, HTTP interface, and SDK surface.
Modules register independently and compose cleanly.
Identity & Access
User registration, authentication, session management with token rotation, role-based access control, and provider bridging.
Education
Course and chapter management, structured content delivery, concept graphs, and atomic publish pipeline.
Enrollment
User-course enrollment tracking with status management, favorites, and activity timestamps.
Progress
Lesson and module progress tracking, assessment result storage with attempt history, and dashboard aggregation.
Commerce
Product catalog, order management, and checkout flow with payment integration.
Subscription
Plan management, payment-integrated checkout, webhook processing, and customer portal.
Storage
File upload and metadata management with cloud-compatible interface. Environment-aware storage backends.
Tenant Isolation
Multi-tenant isolation with subdomain resolution. Tenant-scoped data across all modules.
SEO
Per-page metadata management, dynamic sitemap generation, and robots configuration.
Booking
Appointment scheduling with availability checking, conflict detection, and status management.
A system, not a toolkit.
Direction
Infrastructure that compounds.
Every application built on Tuli strengthens the platform.
Modules developed for one product become available to all future products.
The marginal cost of building new applications decreases over time.
Tuli is the infrastructure layer behind software companies.
Principles
Philosophy
Tuli is designed as infrastructure, not software.
It is built to support products over decades, not launch cycles.
New products are not built from scratch.
They are instantiated.
The goal is not velocity.
The goal is permanence.
Built for companies that build.
If you are building software that requires identity, billing, storage, or structured domain logic — Tuli provides the production backend from day one.
Get in touch