Platform CLI Use cases
Learn
Developer docs User guide Quickstart CLI and AI agents Blog
Company
Services About Contact Links Get started
Real estate

Gablefen Realty: a self-hosted CMS for real estate agencies — an open-source .NET real estate website

A real estate website for a fictional independent brokerage in a mill town, built like the firm's listing window: hanging property cards with house elevations drawn from each listing's style and color, a town plat with pins from content, an open-house board whose lights are worked out on the server, floor plans drawn from a rooms field, recently sold prices, and members-only desks for buyer clients and agents. Built on Raytha, a self-hosted, open-source .NET CMS for real estate agencies and the agencies and freelancers who build their sites.

Build time
Under an hour
Built with
Raytha 2.0.1
Industry
Real estate
Rebuild
One script, from GitHub
Gablefen Realty: a self-hosted CMS for real estate agencies — an open-source .NET real estate website
Walkthrough

See it in action

A short, silent tour of the finished site, recorded from the real pages.

Silent walkthrough, 1080pOpen the MP4
The site

Take the tour

10 screens from the finished site, on desktop and on a phone. Use the arrow keys, swipe, or open any screen full size.

01 / 10Home: the listing window, with hanging cards, elevations drawn from each house's style, and an open-house board worked out on the server
The write-up

For each Raytha use case we take a realistic brief, build the site on a fresh Raytha instance, and publish what comes out: the site, the files behind it, and a kit you can use to rebuild it yourself. This one is a real estate agency website for an independent residential brokerage: the window a buyer studies on a Tuesday evening, the plat a new agent learns the town from, the open-house board a family checks before Saturday, and the members-only desks where buyer clients read their tours and agents keep private remarks. It is written for brokerages that want to run their own site, and for the agencies and freelancers who build those sites for clients.

If you are looking for a self-hosted CMS for real estate agencies, or an open-source .NET CMS for realtor websites, this is the kind of site that fits: listings, neighborhoods, agents, open houses, house styles and sold prices as structured content, server-rendered pages, and a client desk and an agent desk built on Raytha's own user accounts and groups. Built on a fresh Raytha instance, with no client-side app in the layout.

Gablefen Realty is fictional. The town, the firm, the people, the houses and the figures are invented and labeled as such, and phone numbers use the 555 range. There are no offer, payment or sign-up forms; the client and agent accounts exist only for the demo.

A brokerage site built like the listing window

Most people open a real estate website with one question: what is for sale, and when can I walk through? So the home page is the bay window at 12 Courthouse Square, with this week's answers hanging in it.

  • The listing window. Six property cards hang on a rail in a wooden window frame. Each card shows an elevation drawn on the server from the house's style, stories, siding color and roof, so the office changes a card by editing the listing, not the artwork.
  • Open this weekend. Each open house stores a weekday and a start and end time, not a single calendar date, so the board stays current week after week. The lights (happening now, today, this weekend) are worked out on the server from the date and time.
  • The town plat. An illustrated map of Gablefen. Neighborhood washes come from a path stored with each neighborhood, and every home is a numbered pin from its map position, so the office moves a pin by editing content.
  • Listings with a plan. Sixteen homes, for sale, coming soon, under contract or sold. Each has a price, beds, baths, square footage, a file number and a floor plan drawn on the server from a rooms field (floor, name and dimensions). Days on the market are computed from the listed date.
  • Neighborhoods and styles. Five parts of town (Mill Reach, West Common, Ridge Lane, Ferry Green, Courthouse Square) and the house styles that turn up on those streets, each with the listings that belong to them.
  • Recently sold. Closing prices stay on the site so you can see what has actually traded, not just what is asking.
  • A client desk and an agent desk behind sign-in: tours and shortlist notes for buyer clients; a deal board with private remarks, expirations and broker tours for agents.

Design: the listing window

The look is a high-street estate agent's window: cream paper, brick and brass, a dark window frame, and hanging cards. Headings are set in Figtree, body text in Newsreader, and prices, file numbers and labels in IBM Plex Mono. There are no wide display fonts. The elevations, floor plans and plat are generated, so no real house, person or town is pictured.

Why a brokerage, or the agency building for one, looks at a self-hosted CMS

  • The firm owns the listings and the site. A lot of realtor websites live inside a vendor platform, with the brokerage renting the presentation of its own inventory. Raytha is open source. Listings, neighborhoods and agents are content types the firm defines, and the templates and content are files it can keep, hand to the next developer, or move to a new server without renegotiating a contract.
  • It can live with the firm's other systems. Brokerages that already run Windows desktops, Microsoft 365 and a private server often want the public site under the same patching, backup and security review. Raytha is ASP.NET Core with PostgreSQL, so it can run on the firm's own servers or private cloud, with role-based admin permissions and audit logs built in. You can also deploy it on Railway.
  • Client and agent areas without a second product. Raytha has public user accounts and user groups. Bulletins and showing notes carry an audience, and templates check CurrentUser.UserGroups on the server, so a private remark or a shortlist note is never sent to a browser that should not see it. The same feature runs both desks.
  • No per-seat pricing. A small independent firm may have five agents today and twelve next year, and a long list of buyer clients. Every agent and every client can have an account, and Raytha has no seat licensing.
  • A site an agency or freelancer can build and hand off. The content model, the templates and the rebuild kit are ordinary files. The builder can deliver the running site, the repository and a one-command rebuild, and the brokerage can keep it without staying on a proprietary editor.
  • It works next to the MLS and the transaction tools. If the office already uses an MLS feed, a forms product or a transaction desk, those stay where they are. Raytha runs the public site and the members-only desks around them, and its REST API and webhooks can bring in listings or status changes from other systems.

Raytha fits real estate brokerages, and the agencies and freelancers that build for them, that want to own their stack: the code is open source, the content model is yours, and the site can run on servers the firm controls, with client and agent accounts kept in-house. If the brokerage would rather not run it, Raytha can be fully hosted and managed for you under contract. Where another platform may suit you better is if you need a large plugin marketplace, or an all-in-one marketing suite with CRM and marketing automation built in. For fair comparisons with platforms .NET teams often evaluate, see Raytha vs WordPress, Raytha vs Umbraco, Raytha vs DNN and Raytha vs Kentico.

How the members-only desks work

  • Two user groups: clients (buyer clients of the firm) and agents (the brokerage's agents). Each sees its own desk; admins see everything.
  • Bulletins and showings have an audience field (everyone, clients, agents). The detail template reads it and the signed-in user's groups and renders either the content or a lock panel with a sign-in link. Lists show the titles of members-only items with a lock and leave their contents out, and so does search. The page description in the HTML head falls back to a generic line for members-only items, so no summary leaks there either.
  • Private remarks on a listing are rendered only for signed-in agents, on the listing page and on the agent desk.
  • The client desk at /clients is a site page with its own template: signed out, it shows a lock panel; signed in as a buyer client, it shows a client badge, this weekend's tours, shortlist notes and a reminder that offers are written at the office, not through the site.
  • The agent desk at /desk shows the deal board (active and coming listings, days on the market, private remarks), desk notes and agent-only showings, only for agent accounts. A signed-in client sees a short lock if they follow the agent link, and the other way round.
  • Sign-in uses Raytha's built-in login page, restyled to match. There is no registration form: in the story, the office opens a client account after a first meeting, and the broker opens accounts for agents. For more on the pattern, see creating a members-only website.

What is in the kit

Eight content types (listings, neighborhoods, agents, open houses, house styles, landmarks, bulletins, showings), two user groups, site pages for the town plat, recently sold, Buy with us, Sell with us, About, Search, the client desk and the agent desk, and menus, all rebuildable with one command from the kit in the examples repository. Route check: 86 routes checked, 0 failed.

Run it yourself

Run this on your own Raytha

Raytha is free and open source (MIT). Deploy your own copy on Railway, with PostgreSQL included, then load this site into it from the rebuild kit.

  1. Deploy RaythaThe Railway template sets up Raytha, PostgreSQL and a volume for uploads. Open the new site and create your administrator.
  2. Create an API keyIn the admin: People, Admins, open your account, then Create API key.
  3. Import the kitInstall the Raytha CLI, set RAYTHA_URL and RAYTHA_API_KEY, and run the kit's build.sh on the fresh site.

Prefer your own server? Raytha also runs with Docker.

Share Post LinkedIn

Build yours on Raytha

Free, open source and ready to deploy in minutes. Bring a brief and an AI agent.