---
layout: post
title: How DentalRx replaced Firebase and Algolia with Appwrite for 6,000+ users
description: Learn how pharmacist Nickolas Steel moved DentalRx from Firebase and Algolia to Postgres on Appwrite to run a free drug reference for 6,000+ dental users.
date: 2026-11-17
cover: /images/blog/customer-story-dentalrx/cover.avif
timeToRead: 7
author: aditya-oberai
category: customer-stories
featured: false
callToAction: true
faqs:
  - question: "What is DentalRx?"
    answer: "DentalRx is a free drug reference app for dentists and dental students, built by clinical pharmacist Nickolas Steel and focused on Canada. It includes brand and generic drug search, dental-specific drug interactions, treatment guidelines, drug monographs, dosing calculators, and a medication history tool that produces printable patient summaries. It is available on iOS, Android, and the web."
  - question: "How does DentalRx use Appwrite?"
    answer: "DentalRx runs on Appwrite Cloud in the Toronto region. Its drug database lives in [Appwrite's managed PostgreSQL](/docs/products/databases/postgresql), [Appwrite Functions](/docs/products/functions) run backend logic, [Appwrite Messaging](/docs/products/messaging) sends push notifications through [Firebase Cloud Messaging](/docs/products/messaging/fcm), and the Flutter web app is hosted on [Appwrite Sites](/docs/products/sites). The team is also setting up [Appwrite Firewall](/docs/products/firewall) rules, starting from the Console's built-in rule presets."
  - question: "Why did DentalRx move its drug database from Firebase to Postgres?"
    answer: "Drug databases are relational. Each drug starts as a drug concept, with brand names, generic names, and drug classes attached to it. In Firebase's document model, each drug became a static document with subdocuments, and searching a large drug database was expensive enough that DentalRx synced its data to Algolia. Postgres models those relationships directly and handles search itself, which let DentalRx drop Algolia entirely."
  - question: "Can Postgres replace Algolia for search in an app?"
    answer: "For many apps, yes. DentalRx replaced Algolia with a Postgres search extension, and the speed difference was a non-issue in its usability testing, even though Postgres is slower on paper than Algolia's few-millisecond responses. [Appwrite's managed PostgreSQL](/docs/products/databases/postgresql) supports [extensions](/docs/products/databases/postgresql/extensions) such as `pg_trgm` for fuzzy search at no extra cost. A dedicated search service can still be worth it at very large scale, or when search relevance tuning is a product in itself."
  - question: "How do I migrate from Firebase to Appwrite?"
    answer: "Appwrite includes a Firebase migration that imports Firestore data, users, and storage files using a Firebase service account. You run it from the migration wizard in the Appwrite Console. Functions are not migrated automatically, and only top-level Firestore data is imported, so review the [Firebase migration guide](/docs/advanced/migrations/firebase) and its limitations before you start."
  - question: "Can I host a Flutter web app on Appwrite Sites?"
    answer: "Yes. [Appwrite Sites](/docs/products/sites) supports Flutter Web. DentalRx builds its Flutter app as a static web build and hosts it on Sites, while the same codebase ships to the App Store and Google Play. Follow the [Flutter quick start for Sites](/docs/products/sites/quick-start/flutter) to deploy your own, or [sign up for Appwrite Cloud](/sign-in) to get started."
---

From the outside, most medical apps look simple: a search bar, a few lists, a printable report. Nickolas Steel knows the hard part sits underneath, in the drug database.

Nickolas is a clinically trained pharmacist with more than ten years of hospital experience. His day job is in hospital informatics, where he manages the regional drug database and the backend engineering around it.

> "The front end is easy enough. The hard part is all the database and compliance."

Nickolas put that expertise behind [DentalRx](https://dentalrx.ca/dental-app), a free drug reference built for dentistry and used by over 6,000 dentists, dental students, and practices, most of them in Canada. Moving it from Firebase and Algolia to Postgres on Appwrite cleared the way for its next generation of features.

# The challenge

Nickolas grew up close to dentistry. A parent is a dental hygienist, and other relatives work in the field. With a pharmacy background on top of that, the idea was straightforward: help dentists prescribe safely and effectively, so they can help more patients in their practice.

That starts with information, and the information dentists rely on is often inconsistent and hard to find. Answers are spread across drug references and treatment guidelines that don't always agree with each other. Canada and the United States regulate and classify some drugs differently, and the same drug is often sold under different brand names, so a source written for one country may not apply in the other.

Some of those resources are also out of date, and checking them against each other can take hours. A dentist with a patient in the chair doesn't have that time.

# What is DentalRx?

DentalRx gives dentists and dental students a fast, dental-focused way to look up medications and act on what they find. It runs on the web and as a mobile app for iOS and Android.

DentalRx is free to use. Nickolas treats it as a contribution to the dental and healthcare community, in the same spirit as clinicians who publish research and resources to move their field forward.

> "This is quite literally a gesture of goodwill and a free resource for the healthcare field."

![DentalRx home screen with quick search for medications and guidelines, and clinic workflows](/images/blog/customer-story-dentalrx/home.avif "contain")

**Drug search** is what most dentists use DentalRx for. When a patient is taking an unfamiliar drug, a dentist can look it up by generic or brand name and see what it's used for, its drug class and brand names, dental-specific interactions, and dental pearls: short, practical notes to keep in mind before treatment.

![DentalRx search result for amoxicillin with drug class, dental drug interactions, and dental pearls](/images/blog/customer-story-dentalrx/drug-search.avif "contain")

**Treatment guidelines** cover common dental conditions, from dry socket treatment to odontogenic infections. Each one has a quick chairside summary and a detailed view with references. Dental students use them the most, since experienced dentists rarely need to look them up.

![DentalRx treatment guideline for odontogenic infections and abscess in the chairside view](/images/blog/customer-story-dentalrx/guidelines.avif "contain")

**Drug monographs** describe the medications dentists prescribe most often, grouped into categories like anesthetics, analgesics, and antibiotics. Each one lists indications and dosing for different patients, such as a healthy adult, a child, or someone with kidney or liver disease.

![DentalRx monograph for amoxicillin with dosing for adults, children, and patients with kidney or liver disease](/images/blog/customer-story-dentalrx/monograph.avif "contain")

**Dose calculators** work out weight-based doses for children and maximum local anesthetic doses, so a dentist doesn't have to do the math chairside.

![DentalRx pediatric dose calculator showing an amoxicillin prophylaxis dose for a 20 kg patient](/images/blog/customer-story-dentalrx/calculator.avif "contain")

**Medication history** lets dentists enter all of a patient's medications, check them for dental interactions in one pass, and print a summary to add to the patient's chart or hand to the patient.

![DentalRx patient medication history checking ramipril, zopiclone, and sertraline for dental interactions](/images/blog/customer-story-dentalrx/med-history.avif "contain")

The **iOS and Android apps** carry the same tools, with the clinic dashboard, search, and calculators in a bottom navigation bar, so a dentist can look up a drug or work out a maximum anesthetic dose from their phone.

![DentalRx mobile app showing the clinic home screen, quick search, and the maximum anesthetic dose calculator](/images/blog/customer-story-dentalrx/mobile.avif "contain")

# Building DentalRx with Appwrite

Nickolas built the first version of DentalRx in FlutterFlow, with Firebase as the database and Algolia synced alongside it for search. That stack let him ship the product quickly. Over time, however, Firebase became a problem.

Every tool in DentalRx draws on the same drug database. Most drug databases, including the hospital systems Nickolas manages, are organized around a **drug concept**, the core record each drug starts from. Brand names, generic names, and drug classes are separate tables attached to that concept, so a single drug ends up as a web of relationships that differs from country to country. Firebase's document model eventually stopped fitting that structure.

Fixing that started with the app. FlutterFlow can export a project's code, and with today's AI coding tools, Nickolas could take full ownership of that Flutter codebase. Once the app was in his hands, the backend could change too, and Nickolas went looking for something more mature than Firebase.

Appwrite's [migration path from Firebase](/docs/advanced/migrations/firebase) is what first caught the team's attention. Its open-source foundation made the decision easy, and the team never evaluated other Postgres providers like Supabase or Neon.

> "I'm really into open source and being able to own all the data, and Appwrite was just the natural choice there."

The first move kept the data in its old shape: each drug became a single row in Appwrite, and Algolia still handled search.

The second move changed the product. DentalRx now keeps its drug database in [Appwrite's managed PostgreSQL](/docs/products/databases/postgresql), in the Toronto region, close to its Canadian users.

> "Postgres is the gold standard of how drug databases are set up."

In Firebase, every drug was a document with its own subdocuments. Nickolas describes that model as static: each drug was a self-contained record, not part of the web of relationships that Postgres allows. In Postgres, DentalRx models drugs the way hospital databases do, with the drug concept at the center.

That structure shows up in every search. Typing "amoxic" returns each matching drug concept with all of its brand names attached, so a dentist finds the right drug whether they know it as amoxicillin, Amoxil, or Novamoxin.

![DentalRx search results for amoxic showing amoxicillin and related drugs with their brand names](/images/blog/customer-story-dentalrx/search-results.avif "contain")

Search used to need its own service. On Firebase, searching a large drug database document by document was cost-prohibitive, so the team paid for Algolia and kept it in sync with the database.

With Postgres, search moved into the database. Nickolas added a Postgres search [extension](/docs/products/databases/postgresql/extensions) and removed Algolia from the stack completely. The only concern was speed: Algolia answers in a few milliseconds, and Postgres is slower on paper. In usability testing, that difference turned out to be a non-issue.

> "At first I was actually worried that you would be able to notice the lag for Postgres versus Algolia. But honestly, I don't notice at all. It literally is everything that I wanted for the database."

DentalRx now has one fewer vendor to pay and one fewer sync job to maintain. A dedicated search service may make sense at a much larger scale, but at DentalRx's size, it would be over-engineering.

Postgres also opened up a new way to grow the database. DentalRx is built for Canada, but people from other countries still find their way to it, and their searches often use local brand names that are not linked to any drug concept yet.

The plan is to log every search to a dedicated table and send the misses to an AI routine built on Claude. If someone searches for an Indian brand name, for example, the routine will work out which drug concept it belongs to and add the match to a review queue. Once the team approves the match, the brand name is attached to the concept, and the next person who searches for it finds the drug. International users will end up helping build out the database, one search at a time.

Beyond the database, DentalRx uses almost every Appwrite product. The only one it skips is Realtime, because the app does not need it.

- **[Appwrite Functions](/docs/products/functions)** for backend logic
- **[Appwrite Messaging](/docs/products/messaging)** for push notifications, delivered through [Firebase Cloud Messaging](/docs/products/messaging/fcm)
- **[Appwrite Sites](/docs/products/sites)** to host the Flutter web app as a static build, while the same Flutter codebase ships to the App Store and Google Play
- **[Appwrite Firewall](/docs/products/firewall)** for traffic rules, which the team has started setting up from the Console's built-in presets for OTP abuse protection, regional compliance, and scraping prevention

Domains are the last piece. DentalRx still manages most of its domains on Cloudflare, and Nickolas wants to bring them into Appwrite so the entire stack lives in one place. That matters for how he works: once everything is in Appwrite, an AI agent can make changes across the whole stack through the [Appwrite CLI](/docs/tooling/command-line/installation).

> "I can literally just point the agent to the CLI and be like, hey, make these changes, go ahead and do what you're scoped to do, and it'll just do it. Then I can just keep my work to the terminal or keep my work to the IDE."

# DentalRx today

DentalRx has passed **6,000 lifetime users**, a mix of dental students, dental practices, and individual dentists. All of that growth is organic. The team does no marketing for the app, and new users still sign up every day.

The biggest feature on the roadmap is prescriptions, which is temporarily switched off while it's rebuilt on the new Postgres backend. On top of each drug concept, the team is attaching the same building blocks hospitals use for prescribing. The data is ready. What remains is a clinical review of every entry and working through the legal requirements of prescribing.

Along the way, Nickolas has become one of Appwrite's most vocal advocates, recommending it to every developer he knows and moving a dental tech startup he works with onto it as well.

> "We're a small team, so every extra SaaS or layer of infrastructure slows down how fast we can ship. With Appwrite, everything we need is already there, so there's nothing between building something and shipping it. If you're bootstrapping your project, or building your startup, that's a huge win."

DentalRx shows what happens when deep domain expertise meets a backend that gets out of the way: a pharmacist built a clinical reference used by thousands, then rebuilt its data layer around the model the medical world already trusts. Learn more about DentalRx by visiting their [website](https://dentalrx.ca/dental-app).
