Skip to content
Back to the portfolio

OliBase: Micro BaaS

  • MongoDB
  • Express
  • React
  • Node.js
  • Redis
  • REST API
  • TypeScript

I had been building small MERN (MongoDB, Express, React, Node) projects, and they worked, but none of them forced me to make real architecture decisions. I wanted to get past the tutorial stage, refactor, and understand why things work the way they do.

The inspiration came from Backends as a Service (BaaS) like Firebase and Supabase. The idea was to build a simplified clone of them, OliBase, as a study project with no plans to turn it into a commercial product.

The rule from day one: be truly multi-tenant. That meant two separate authentication systems, one for dashboard users (administrators) and one for the end users of each application. Security came from API keys tied to each project and JWTs with strict ownership checks. This is where I dug deep into auth flows, API security, and separation of concerns.

The turning point was building my own data layer, with dynamic collections and documents. On top of it I added Row Level Security (RLS), inspired by Supabase: each user only reaches their own data, and one project never sees another project's data. Every RLS rule took testing and middleware tweaks, and that's when I saw how much a real backend involves.

To manage all of this, I built a React dashboard that consumes OliBase's own API (Node, Express, and MongoDB). From there you can manage projects, end users, collections, and RLS rules, and read the execution logs.

The final test was Eventum, a real client app. It authenticates users through OliBase, runs CRUD operations protected by RLS, and generates logs that show up in the dashboard. That's how I saw OliBase working outside of theory, with an actual application running on top of it.

Full post on the blog: https://www.mmlo.com.br/blog/odisseia-do-olibase