Seeking Bubble Technical Partner + Developer Collaborators — GestEdu EdTech SaaS

Hi Bubble Community,

I’m building GestEdu, a configurable, multi-tenant school-management SaaS designed initially for Angola, with the architecture and long-term vision to expand into Namibia and other African markets.

GestEdu is designed to bring several critical school operations into one platform:

• Student and staff management
• Classes, subjects and enrolment
• Assessments, grades and report cards
• Attendance
• School fees and student billing
• Payments, receipts and outstanding balances
• Income and expense management
• Administrator, teacher, parent and student portals
• Reporting and school analytics

This is not just an idea. Product planning is already well advanced, an initial Bubble application exists, and we have developed a detailed Product Requirements Document covering the MVP, product architecture, finance system, multi-tenancy, internationalisation and roadmap.

I’m looking for two kinds of people:

1. Potential Technical Partner / Co-founder

I’m interested in meeting an experienced Bubble developer or technical product builder who is interested in the longer-term journey.

The ideal person understands:

• scalable Bubble architecture
• multi-tenant SaaS
• database architecture
• privacy rules and security
• backend workflows
• performance optimisation
• APIs and integrations
• technical leadership

I’m not looking to give away a co-founder title after one conversation. I’d like us to work together first, validate compatibility and gradually explore a deeper partnership if there is a strong fit.

2. Bubble Developer Collaborators

I’m also building a small group of developers who can contribute to defined GestEdu workstreams, including:

• SaaS architecture
• Academic management
• Finance and payments
• Responsive UI/UX
• Reporting/PDF generation
• APIs and integrations
• QA and security

Different collaboration arrangements may be possible depending on experience, commitment and responsibility, including project/milestone work, longer-term paid opportunities as the project develops, and other structured collaboration models.

Why GestEdu?

The objective isn’t to build a school app for one institution.

We’re designing GestEdu as a configuration-driven platform for different African education systems.

For example, an Angolan school may operate in Portuguese, use AOA and its own assessment structure, while a Namibian school may operate in English, use NAD and have a different academic system — without requiring separate applications.

If you’re interested

Please DM me with:

  1. Your Bubble experience
  2. Portfolio/live Bubble applications
  3. Experience with SaaS or management systems
  4. Database/privacy architecture experience
  5. Your strongest technical areas
  6. Weekly availability
  7. Whether you’re interested in project collaboration, a core-team role or potentially a longer-term technical partnership
  8. Your preferred compensation/collaboration model

I’m particularly interested in people who care about building a maintainable product, not just shipping screens quickly.

Product: GestEdu
Sector: EdTech / School Management SaaS
Initial market: Angola
Expansion vision: African markets
Technology: Bubble

If the mission and technical challenge interest you, I’d be happy to talk.

Hi
have 2+ years of Bubble experience, including SaaS products, APIs, payments, backend workflows, and AI integrations. I would be interested in contributing as a Bubble developer collaborator and would be happy to discuss the project.
Check your DM also.

This isn’t doable on Bubble unless your students are 16 and older. Bubble’s DPA does not allow it.

Hi, I’m interested in contributing to GestEdu. I have 4 years of professional Bubble.io experience, with experience building SaaS and management systems, database architecture, APIs, workflows, and privacy/security rules.

I’d be happy to discuss potential collaboration and see if there’s a good fit.

Hi,

Multi-tenant is the part that decides whether this product survives at scale, so I will start there.

Configuration-driven multi-tenancy on Bubble usually breaks in one of two places: privacy rules that gate the UI instead of the data, and a schema where tenant separation is implied rather than enforced. Once a school in Namibia and a school in Angola share the same tables with different currencies, assessment structures and languages, any gap there becomes a data leak between institutions rather than a cosmetic bug. That is the first thing I would want to review in the existing app.

My background: six years on Bubble, 15+ production apps, mostly systems with user roles, permissions, billing and reporting rather than simple CRUD. I work spec-first: data model, roles, scenarios and acceptance criteria before building, which is close to how you describe your PRD.

Recent relevant work: a two-sided marketplace with escrow payments and tiered commissions, and management systems with multiple user roles and financial records.

Availability: I can commit to defined workstreams weekly. On compensation, I am looking for paid project or milestone work. I am open to discussing a deeper partnership later, but only after we have actually worked together and both sides know what they are getting.

Strongest areas: database and privacy architecture, multi-tenant structure, backend workflows, API integrations.

Happy to look at the existing app and the PRD and give you an honest read on the architecture before anything else.

ClubHub’s privacy policy states that it collects information for children under 13 years old yet Bubble’s DPA restricts collection of personal data for children under the age of 16. Even using an external database, which you don’t seem to be using, wouldn’t make you compliant as far as I know. Is this an oversight or are there exceptions/workarounds that I’m not aware of? Recently dealt with this for a client and we’re now evaluating other solutions to move off Bubble.

ClubHub is on an Enterprise plan w/ dedicated server and may well have its own arrangements with Bubble.

Are you aware of cases where Bubble offers exceptions to their DPA for enterprise plans? We were in communication with Bubble support this week and asked:

If Bubble’s standard contractual framework does not permit this processing, does Bubble offer an enterprise agreement, education-specific arrangement, dedicated infrastructure option, or other solution that would permit it? If so, what steps would we need to take?

The response we received:

Under Section 13.4(g) of Bubble’s DPA, customers may not submit personal data relating to children under 16 to Bubble’s services. This requirement applies across the scenarios you described.

No I’m just saying best not to speculate

Just want to clarify what’s possible as it’s relevant to an ongoing situation with one of my clients. Also think it’s important for OP and others like him to know that they may be sinking tens of thousands of dollars into a build that violates Bubble’s terms.

Yeah I wouldn’t trust their support’s answer unless it was sales or adjacent. Their support has misguided information from my experience.

Hi Edgar,

I read your post and the replies. The two objections raised in the thread, student data for minors and multi-tenancy, are the real ones. They’re also the two things Bubble handles worst.

I’m Faraz, a full-stack JavaScript dev (Next.js, React, TypeScript, Node, Express, Postgres). For the last 3 years I’ve built and run my own education SaaS, Parhako, a test-prep platform for Pakistan’s entrance exams. Everything solo: three frontends, one backend, billing, student portals, analytics, and an AI pipeline that generates the course content. Payments run without Stripe, because Stripe doesn’t operate here. You will face the same problem with AOA and NAD. That part is solvable, I’ve lived it.

Multi-tenant in real code is a Postgres design problem, row-level security, tenant-scoped data. Doable properly. In Bubble it stays a workaround, which is what the replies above are circling around.

On Upwork I’m 5.0 across every contract I’ve taken, one ran 942 hours.

I’m not pitching a co-founder title. Your work-first approach is the right one. I’d start with milestone work on the two hardest workstreams in your list, SaaS architecture and finance/payments.

Two questions before anything else. What budget range are you carrying for the first milestones? And is real code instead of Bubble on the table for you, or is Bubble the commitment?

Faraz faraz-35 (Faraz Shah) · GitHub

I’m a Bubble.io Full-Stack Developer with 5.6+ years of professional experience. I work on both frontend and backend development, including database architecture, workflows, APIs, privacy rules, responsive UI, integrations, debugging, and performance optimisation.