About Dashify

Dashify is a multi tenant SaaS platform for organisations that want to run their day to day operations from one place. Project management, HR, billing, knowledge sharing, real time chat, AI assistance, file storage, all under one roof, all in one codebase, all with the same login.

It is built solo. It is in production. It is opinionated about safety, performance, and clarity.

What "multi tenant" really means

Imagine a tall apartment building. The building is one piece of architecture, one set of plumbing, one electrical grid, one elevator. But each apartment is a separate home. The neighbour next door cannot walk into your living room. The neighbour above cannot hear your conversations. The doors lock independently. The post for unit 4-B never lands in unit 7-A's mailbox.

Dashify is the apartment building. Every customer organisation is an apartment. They share the codebase, the database server, the message queues, even the AI brain, but none of their data ever touches another organisation's data. Not by accident, not by misconfiguration, not by a clever attack. The walls are baked into the platform itself.

That is the single most important promise Dashify makes, and most of the architecture exists to keep that promise.

Who Dashify is for

• Internal teams at a company that wants its own private, branded operations hub.
• Software vendors that want to white-label a complete back-office for their customers.
• Builders and learners who want to read a real, deeply-engineered SaaS codebase end to end.

If you are the third group, this documentation is mostly for you. Every page is written in plain language, with a diagram or two where helpful, and never with code unless the topic literally is "here is the command you type."

What's inside

At the highest level Dashify is:

• A browser app built with React, TypeScript, and Vite, delivered as a Progressive Web App so users can install it like a native app and keep working briefly when offline.
• An API server built with Node.js and Express, written in TypeScript, that handles every request, every login, every permission check.
• A worker process that quietly handles the slow stuff (sending emails, generating PDFs, indexing documents for AI search) so the API stays snappy.
• A document database (MongoDB) for storing the world.
• A fast cache and message broker (Redis) for sessions, rate limiting, real time fanout, and queue plumbing.
• An on premise AI brain (Ollama running Qwen 2.5 + Qdrant for vector search) so users can ask questions about their own data without anything leaving the building.

Every one of those pieces gets its own dedicated page in this documentation, written for a reader who has not seen the code.

The four convictions Dashify is built on

1. Tenant isolation is non-negotiable. Every database query passes through a layer that automatically attaches the current organisation's id. There is no way to "forget" the tenant filter. The few queries that are explicitly cross tenant are loud and reviewed.

2. Security is layered. Httpsonly cookies, CSRF double submit, content security policy, rate limiting, audit logging, secure headers, input validation, encrypted secrets at rest. No single defence is asked to carry the whole weight.

3. The system explains itself. Every action a privileged user takes is logged. Every error has structured context. Every long task is observable from a dashboard. The platform should never be a black box, even to its own author.

4. Plain language wherever possible. This documentation is the last conviction made visible. If a concept needs a metaphor or a diagram to land, it gets one.

What this documentation covers

The sidebar is the table of contents. In rough order:

1. Welcome, this page, plus an introduction to the person who built it.
2. Getting Started, how to clone, install, run locally, and deploy.
3. Architecture, the big picture, the tech stack, multi tenancy explained with a longer metaphor.
4. Database, MongoDB, tenant isolation, indexing, and Redis caching.
5. Authentication, twelve pages, one concept at a time, from "what is a password" up through SSO and SCIM.
6. Security, every shield Dashify carries and what each one blocks.
7. Scalability, how the platform grows.
8. The Future, what is next and what is missing.

A note on the scope

Dashify is a real product, not a demo. That means not every corner is polished, not every test is written, and the roadmap is real. The "Future" section is honest about what is missing and what would come next. Read it.

Key takeaways

• Dashify is a multi tenant SaaS that shares one codebase across many organisations.
• The single most important rule is that no organisation's data ever touches another's.
• The rest of this documentation explains, plainly, every piece that makes that rule hold.