My workProjectsTasksCRMMarketingPeople+ Your module
Your product
Your modules: what makes your product unique. It is the only thing you build; the example is Timelogbook’s seven.
Tlog SaaS Accelerator Platform
The multi-tenant foundation Timelogbook is built on. If you're launching your own SaaS product, you don't have to rebuild the infrastructure for accounts, access and modules: you build only what makes your product unique.
Your productYou build it
- My work
- Projects
- Tasks
- CRM
- Marketing
- People
- Billing
- Console
Example: Timelogbook's eight modules.
Each tenantConfigurable
- Enabled modules
- Feature flags
- Access domains
PlatformAlready solved
- Data separated by tenant
- Identity and two-factor
- Roles and permissions
- Sessions
- Backoffice
What you customize and what stays solved
The platform separates what is yours from what any SaaS product has in common. What is common is never built again.
What you bring
- Your modules. The functionality that makes your product different.
- What each tenant gets. Which modules and feature flags each client has enabled.
- The domains. Each client signs in through its own access domains.
- Permissions by area. What each role sees inside your product.
What the platform already solves
- Multi-tenant. Each client is a tenant with its data kept separate.
- Identity. Login and mandatory two-factor authentication.
- Roles and permissions. The foundation for deciding who gets access to what.
- Sessions. A console to see open sessions and sign them out.
- Backoffice. Platform users invited by email, to operate tenants without touching the database.
The three layers, one by one
This is what each layer looks like and how they work together when someone enters your product.
a.example.com
b.example.com
c.example.com
Each tenant
Each client signs in through its own domain and sees only the modules and feature flags it has enabled. It is configured, not rebuilt.
Data separated by tenantIdentity and two-factorRoles and permissionsSessionsBackoffice
Already solved
Platform
What every SaaS product has in common: identity, permissions, sessions, separated data and a backoffice. It is the same base Timelogbook runs on.
What happens when a person signs in
- A person signs inThrough its client’s domain.
- The platform identifies themWith two-factor.
- The configuration appliesThat tenant’s modules and flags.
- Their role decides what they seePermissions by area.
- They see only their dataKept apart from other tenants.
Each client, its own configuration
One product, different tenants: each one signs in through its own domain and sees only the modules it has enabled.
Tenant ATenant BTenant C
Access domaina.example.comb.example.comc.example.com
ProjectsEnabledEnabledEnabled
BillingEnabledEnabledDisabled
CRMDisabledEnabledDisabled
MarketingEnabledEnabledDisabled
TasksEnabledDisabledEnabled
Sample data.
Who it's for
Teams launching a SaaS product
They start on a multi-tenant base instead of building their own.
Scale-ups
They move from an architecture designed for a single client to one designed for many.
Companies with a new digital product
They launch it without touching the main product.
The example: Timelogbook
Timelogbook is the ERP for IT services companies and the first product built on the platform. It's a separate product, with its own page. The second vertical is Marketing: demand generation for B2B teams, reusing CRM, People, Billing and Console from the first and adding its own.
Built on the platform
PDS: fire protection inspections
PDS (Protection Detection Systems) inspects fire protection systems in Calgary, Canada. Its software looks nothing like Timelogbook and runs on the same platform: PDS built only what is specific to its business.
Screenshots of the PDS app with sample data.
What PDS built
- Buildings. Each building with its floors, zones and devices: extinguishers, detectors, sprinklers, alarm panels.
- Inspection templates. The tests each device type needs, following NFPA and CAN/ULC.
- Deficiencies and remediations. Whatever fails is recorded and tracked until it is fixed.
- Reports. Versioned PDF report layouts: once published, they don’t change.
- Technician app. A mobile app for inspecting on site.
What the platform already had
- Multi-tenant. Several inspection companies, each with its data kept separate.
- Identity. Sign-in, tokens and the API gateway.
- Roles and permissions. What each person in the office and in the field can see.
- Directory. People synced from Microsoft Entra ID.
- Shared services. Email, scheduled tasks and technicians’ time tracking.
Let's talk about your product
Tell us what you want to launch and we'll explain how it fits on the platform.