Zettla.com | Real Estate Product Development
Oleksandr Murmylo
Zettla | Real estate platform built with Framer + Supabase
Connected real estate platform combining listings, accounts, saved properties, bookings, alerts, services, and custom workflows.
Building a real estate product on top of Framer
Zettla started as a real estate website and gradually became a much larger product.
The platform now connects property discovery, authenticated accounts, saved listings, bookings, payment plan requests, property alerts, service providers, email flows, and backend automation.
Framer remains the frontend, while Supabase and other tools handle the product logic behind it.
Property discovery
The core experience is built around helping users find and compare properties.
Listings include property type, location, pricing, bedrooms, bathrooms, square meterage, neighbourhoods, investment details, delivery dates, and other property-specific data.
Custom filtering makes it easier to narrow a large inventory without turning the experience into a complicated property database.
Framer as the frontend
Framer gave us the speed and flexibility needed for the public-facing experience.
But features such as authentication, bookmarks, alerts, bookings, and user-specific data needed a proper backend.
Instead of forcing everything into Framer CMS, the architecture separates presentation from application logic.
Framer handles the interface and content experience.
Supabase handles authentication, databases, user data, and backend logic.
Authentication and user profiles
Users can create accounts, sign in, recover passwords, and manage their profile.
Authentication also unlocks functionality that depends on the user, including saved properties and communication preferences.
This created a persistent experience rather than relying on browser-based state.
Saved properties
Users can bookmark listings and return to them later.
Saved properties are tied to the authenticated account and stored in Supabase, so bookmarks remain available across sessions and devices.
Property information is mirrored into a normalized data layer where needed, allowing the account experience to work independently from the presentation layer in Framer CMS.
Booking flows
Zettla needed several booking experiences rather than one generic calendar.
Flows were created for property calls, online viewings, onsite viewings, consultations, and service-provider appointments.
The setup connects:
Framer → Supabase → n8n → Cal.com
This allowed the UI to stay inside the website while booking availability and workflow logic could be handled externally.
Payment plan requests
Investment properties can have more complex payment structures.
A custom payment plan flow was built so users can submit a request linked to the exact property and floor plan they are viewing.
The request captures the relevant property data, validates the user and submission, stores the request, and forwards it into the automation flow for follow-up.
Property alerts
Users can also stay updated after leaving the website.
The alert system supports events such as:
New properties
Price changes
Sold properties
Removed listings
Properties returning to market
The backend detects relevant property changes and triggers the appropriate email workflow.
Email and automation infrastructure
Transactional and product communication is handled through Resend, while n8n connects workflows between different parts of the platform.
Automations support booking events, property alerts, contact syncing, provider workflows, and other operational processes.
This keeps heavy workflow logic outside the Framer project and makes the system easier to extend.
Service provider ecosystem
Zettla also expanded beyond listings.
Users can discover local service providers related to moving, property ownership, relocation, and everyday life.
The provider system includes categories, locations, services, onboarding workflows, booking flows, and provider-specific data.
That turns Zettla from a property search website into a broader relocation platform.
CMS and data architecture
One of the biggest challenges was deciding what belongs in Framer and what should live in the backend.
Framer CMS remains the right place for content that needs to be edited and presented visually.
Supabase stores structured data required by application features such as authentication, bookmarks, alerts, user preferences, and transactional workflows.
Sync processes connect both layers where necessary.
This keeps the website easy to manage without making Framer responsible for backend functionality it was never designed for.
The result
Zettla became much more than a marketing website.
The final ecosystem combines:
Property listings and filtering
Authentication and profiles
Saved properties
Property alerts
Booking flows
Payment plan requests
Service providers
Email infrastructure
Automations
Analytics and tracking
The project shows how Framer can work as the frontend of a much larger product when the architecture behind it is handled properly.
Project info
Role
Product design, Framer development, product architecture
Frontend
Framer
Backend
Supabase
Automation
n8n
Email
Resend
Booking
Cal.com
Scope
CMS, authentication, property data, bookmarks, alerts, bookings, payment flows, service providers, integrations, analytics, custom components
Industry
Proptech / Real Estate
Website
zettla.com
Planning a more advanced Framer build?
If your project needs more than a marketing website, including authentication, CMS, backend integrations, bookings, automations, or custom product functionality, feel free to reach out.
Like this project
Posted Sep 1, 2026
Built Zettla as a connected real estate product using Framer, Supabase, n8n, auth, booking flows, property alerts, and custom backend logic.
Likes
0
Views
9
Timeline
Jun 1, 2026 - Sep 1, 2026
