OPEN-SOURCE · SELF-HOSTABLE · BUILT FOR INDIA

Real-estate operations.
On your terms.

OpenEstate brings property sales workflows into one system—from the first inquiry and inventory selection to booking, financial records, and customer or broker follow-up.

AGPL-3.0-onlySelf-hostedPlugin-ready
OPENESTATE / WORKSPACEILLUSTRATIVE UI
WORKSPACE / OVERVIEW

Sales operations

SAMPLE LAYOUT
LEAD PIPELINEInquiry → BookingConfigurable stages
INVENTORYUnits & plotsProjects and pricing
FINANCIALSLedger entriesAppend-only records
Lead journeyWORKFLOW
New inquiry
Follow-up
Negotiation
Booking
Connected workflowsROLES
S
Staff workspaceLeads · inventory · sales
C
Customer portalBookings · documents
B
Broker portalCommissions · statements

Conceptual preview for illustration — not a live application screenshot or live demo.

BUILT TO BE INSPECTEDBUILT TO BE SELF-HOSTEDBUILT TO BE EXTENDED

THE IDEA

One operational record.
Fewer broken handoffs.

Property teams often spread inquiries, inventory, booking details, payments, and customer communication across disconnected tools. OpenEstate is built to bring those workflows into a coherent, inspectable system that your team can run on infrastructure it controls.

OpenEstate is under active development. The repository describes the core sales funnel as ready for an initial pilot, with known gaps documented before real-project use.

CAPABILITIES

From inquiry to
post-sales service.

Features below are based on the project README and documented implementation status. Review the known gaps before relying on it for a live project.

01
↗

Pre-sales CRM

Capture and assign inquiries, manage configurable lead stages, record follow-ups, and review funnel reports.

Explore source ↗
02
⌂

Property inventory

Model projects, towers, floors, and units, including plotted and farmhouse land inventory with pricing.

Explore source ↗
03
≋

Post-sales ledger

Track bookings, payment plans, installments, receipts, and financial corrections through append-only ledger entries.

Explore source ↗
04
◎

Customer & broker portals

Separate portal experiences for bookings, documents, statements, support tickets, and broker commissions.

Explore source ↗
05
⌘

Extensibility

Use custom fields, module flags, configurable terminology, plugins, and webhooks to adapt workflows.

Explore source ↗
06
⌑

Self-hosted control

Run the application on your own Linux server with PostgreSQL, Redis, and nginx that you manage.

Read installation guide ↗

HOW IT FITS TOGETHER

A connected journey,
step by step.

OpenEstate follows the property-sales lifecycle, with different roles working from the same underlying records.

Read the architecture ↗
01

Capture & assign

Bring in inquiries, assign ownership, and track the lead stage and next follow-up.

↗
02

Manage inventory

Organize property projects and available units or plots with configurable pricing.

↗
03

Book & reconcile

Create bookings and payment plans, post receipts, and preserve financial changes as ledger entries.

↗
04

Support the relationship

Give customers and brokers portal access to the information relevant to their role.

↗

DESIGN PRINCIPLES

Control at the core.
Flexibility at the edges.

OpenEstate emphasizes ownership, auditable records, tenant separation, and extension points instead of requiring a custom fork for every workflow.

01 / OWNERSHIP

Your infrastructure

No mandatory SaaS dependency. You manage the server and the supporting PostgreSQL, Redis, and nginx services.

02 / ACCOUNTABILITY

Ledger-based finance

Financial records are append-only; corrections use reversal entries and balances are computed from the ledger.

03 / ISOLATION

Tenant-aware architecture

Company data isolation is enforced using PostgreSQL row-level security alongside application controls.

04 / EXTENSION

Plugins, not forks

Custom fields, webhooks, module flags, terminology settings, and a plugin API support adaptation.

ENTRYWeb browsersStaff · Customer · Broker
→
APPLICATIONOpenEstateReact interfaces · NestJS API
→
DATA SERVICESPostgreSQL + RedisRecords · queues

Simplified from the repository architecture. nginx serves the frontend assets and reverse-proxies API requests.

GET STARTED

Try it on a server
you control.

The documented native installation targets Ubuntu and expects you to install and manage PostgreSQL, Redis, and nginx first. Follow the installation guide and release notes before using a live project.

NATIVE INSTALL · UBUNTU
sudo git clone https://github.com/stemAGH/openestate.git /opt/openestate-src
cd /opt/openestate-src/deploy/native
sudo ./install-native.sh --server-name crm.yourcompany.com
Replace the example hostname with one that resolves to your server.

PROJECT STATUS

Built, tested, and still evolving.

The repository identifies v0.8.4 as a pilot-ready core sales funnel and documents known gaps and security-related release notes. This is not presented as a hosted public demo.

Review known gaps before use ↗

EXPLORE THE PROJECT

See what’s in the code.
Help shape what comes next.

Read the docs, inspect the implementation, report an issue, or contribute through the project’s documented process.