How BeeAPro ships new features daily on Supabase with a technical team of three

I would suggest Supabase for any new application. It scales well and just works in production.

Arianna Bruni, CEO of BeeAPro

BeeAPro is an Italian training platform for companies in compliance-heavy industries, such as finance, legal, and IT. Trainers upload their documents, slides, and videos, and AI helps them turn that material into short, interactive lessons for their company's employees. Learners answer questions to unlock the next lesson, practice in a text-based role-play game, and earn a certification at the end. For the companies that use it, BeeAPro is a complete training platform that covers building the course and certifying the people who take it.

The founding team started the company in 2025. They saw a common problem: companies have piles of process and compliance documents, and no way to know if employees understood them.

Rebuilding the product for production#

The first version of BeeAPro ran on a custom microservice platform, with a front end the team built themselves. It did not work for users or for the team.

The first version of BeeAPro was really ugly. It was hard to use and hard to maintain.

Arianna Bruni, CEO of BeeAPro

The team dropped it and rethought the product. For the second version, they built a prototype of the BeeAPro platform on Lovable, which uses Supabase as its backend. A month later, in September 2025, they saw that Lovable could not get them to a production-ready platform with their setup. So they took the code out of Lovable, started their own development process, and kept Supabase as the backend.

A production-ready backend built for stability and scale#

BeeAPro founders knew what a production-ready solution looked like. They had previously built and run an insurance platform on MongoDB Atlas. It handles around 60 million motor insurance quotations a month, in a heavily regulated industry. Then they measured Supabase against that experience and made the technical call themselves.

I know very well when something is ready for production. Supabase has proven itself to be a stable platform that we can reliably use and build on.

Nitin Govardhane, Software Engineer at BeeAPro

Stability got Supabase in the door. Beyond that, the team values the open-source core Supabase built its business around, and above all the support from the Supabase team. BeeAPro's technical team is lean, with three people, so a quick answer from someone who knows the platform matters more to them than any single feature.

Above the technology, the support is really responsive. We get a response immediately, and we have an engineer to talk to about our problems. For me, this is the most important thing.

Arianna Bruni, CEO of BeeAPro

One Supabase project behind every company's courses#

BeeAPro runs its whole backend on one Supabase project. Postgres holds the data, Storage holds the videos and documents, and Auth handles every login. The team splits the rest of its logic by where it runs. Postgres functions work on BeeAPro's own data. Edge Functions reach outside it to AI providers, email providers, and more complex workflows. Each new feature becomes a new Edge Function, which works like a small microservice.

Keeping every company's data apart#

What keeps this safe for compliance-minded companies is Row Level Security. BeeAPro keeps every company in the same tables and lets the database decide who sees what.

We have one table with the courses. We slice that table using Row Level Security, so we can say this company can access this course, and this other company can access these courses.

Emily Sofia Menghi, Marketing Manager at BeeAPro

The team applies the same approach to almost every table, which keeps the data structure simple even though each new feature ships with a migration.

That design is what lets BeeAPro serve Nethesis, its first customer. Nethesis is an Italian open-source company with about 600 partners and 35,000 users. It sits at the top of BeeAPro's multi-level model and creates sub-companies on the platform. Each of those can create more, and courses move down the chain.

Shipping features without building plumbing#

The rest of the stack is there so the team can spend its time shipping features instead of building plumbing. Auth is the clearest example. It came with an interface to disable users and a record of when each user logged in, both things the team would otherwise have built by hand.

Edge Functions work the same way. They build on those same authenticated users, so a new feature is a new function, which keeps the release loop short. Branching gives each feature a running copy of the application to test before it reaches production. The team builds with Claude Code, and the whole process is fully automated.

Every time we deploy a new feature, we build a new application on the fly, we test it, and when everything is fine, we deploy in production.

Nitin Govardhane, Software Engineer at BeeAPro

Daily releases from a team of three#

That setup pays off in speed.

We deploy new features a couple of times per day, so our development process is really quick.

Emily Sofia Menghi, Marketing Manager at BeeAPro

Since going into production in May 2026, BeeAPro has grown to about 2,000 customers. A technical team of three runs the platform inside a company of 10 people.

Nethesis chose BeeAPro to distribute cybersecurity and NIS2 compliance courses across its network. The rollout is going step by step, and the goal is to activate all 35,000 Nethesis users on the platform.

What is next: investing in sales and marketing#

With the platform ready, BeeAPro plans to put its investment into sales and marketing over the next 12 months.

The platform is ready. We know we can scale easily with Supabase, so we can just add additional servers when needed.

Emily Sofia Menghi, Marketing Manager at BeeAPro

Hiring will follow the workload. The founders expect new companies to ask for new features, and that may mean more developers.

BeeAPro reached this point fully bootstrapped, with a small team. The founding team's advice to other founders is to start with sales. Finding a user who can give you feedback matters as much as the architecture you build. A production-ready app is different from a first app, they say, so put security, functionality, and reliability first and choose a toolkit that lets you build with those priorities in mind.

Key results#

• Ships new features to production a couple of times per day, with a Supabase branch for every feature
• Approximately 2,000 customers since launching in production in May 2026
• A technical team of three, one founder and two developers, runs the platform for a company of 10 people with support from Supabase
• One courses table serves every company, and Row Level Security keeps their content apart