Server for Real Estate CRM & Property Portal in India
By Rohit, Founder ·
Quick answer: A real estate agency does not need a powerful server; it needs a reliable, well-backed-up one. The workload is a CRM (leads, follow-ups, site visits, bookings), a property-listing website or portal, and a large archive of photos, brochures, floor plans and agreements. That is light on CPU and heavy on storage, backups and uptime. For a single office or a few branches, a Starter- or Pro-class server with ECC memory, NVMe storage for the CRM database, a separate disk array for media, and an off-server backup is typically enough. The popular open-source CRMs publish software requirements (for example, EspoCRM lists PHP 8.3–8.5 and MySQL 8.0+, MariaDB 10.3+ or PostgreSQL 15) but no single hardware minimum, so size by number of users and amount of media, not by a headline spec.
This guide is for property brokerages, channel-partner firms, builders' sales offices and rental or property-management companies in India that are deciding whether to run their CRM and listing portal on their own server instead of, or alongside, rented cloud software. It explains what the workload actually needs, what Indian rules touch the data you hold, and when a self-hosted server is the right call and when it is not.
What Does a Real Estate Agency Actually Run?
Before choosing hardware, list the systems. Most agencies end up with some mix of the following.
| System | What it does | What it stresses |
|---|---|---|
| CRM | Captures leads from portals, ads, WhatsApp and walk-ins; assigns them to agents; tracks calls, site visits and bookings | Database reads/writes, many simultaneous users, background jobs (email, reminders) |
| Property listing site or portal | Publishes projects and listings with photos, maps and enquiry forms | Web server, image delivery, traffic spikes after a campaign |
| Media and document archive | Stores photos, walkthrough videos, brochures, floor plans, KYC and agreement copies | Disk capacity, backup time, access control |
| Accounts and back-office | Invoices, commission tracking, payroll | Small database; high importance, low load |
| Internal tools | File shares, email, call-recording storage, dashboards | Storage and network |
Notice what is missing: heavy computation. None of this needs a GPU or a high core count. If you also run AI features such as lead scoring or automatic listing descriptions, those usually call an external service and do not change the sizing of the core server.
What the CRM Software Itself Asks For
Open-source CRMs that agencies commonly self-host are well documented on the software side. EspoCRM's server documentation, for example, lists:
- PHP 8.3 to 8.5 and a database of MySQL 8.0+, MariaDB 10.3+ or PostgreSQL 15;
- recommended PHP settings of
memory_limit = 256M,post_max_size = 50Mandupload_max_filesize = 50M; - a scheduled-jobs setup (crontab on Linux) so reminders and email imports run in the background.
The same documentation says a VPS or dedicated server suits production best. Frappe CRM, SuiteCRM and Odoo have their own version requirements; check the vendor's page for the release you plan to run. What none of them gives you is one universal "you need X GB of RAM" figure, because the answer depends on how many people use the system at once, how many records it holds and how many attachments are stored. We have not benchmarked these products on ProStation hardware, so the sizing table later in this guide is planning guidance, not measured performance.
Why Storage, Not CPU, Is the Real Constraint
A property portal grows by accumulating media. As an illustration only (your numbers will differ): if an agency lists 2,000 properties, each with 20 photos averaging 3 MB, that is about 120 GB of original photos before any brochures, videos or documents. Add walkthrough videos and scanned agreements and a few hundred gigabytes is ordinary. Three consequences follow.
- Keep the CRM database on fast storage and the media on cheaper, larger storage. NVMe suits the database and operating system; large HDDs in a redundant array suit the archive. Our NVMe, SAS and SATA guide explains the trade-offs.
- Use RAID for uptime, and do not mistake it for backup. RAID keeps the server running when a disk fails; it does not protect against deletion, ransomware or a fire. See RAID levels explained.
- Plan for growth. Choose a chassis with spare drive bays so you can add capacity instead of replacing the machine. If you mainly need shared storage for branch offices, our NAS storage server guide covers that design.
Indian Rules That Touch the Data You Hold
This section is general information, not legal advice; confirm specifics with a qualified adviser.
RERA: record keeping for agents
Under Section 9 of the Real Estate (Regulation and Development) Act, 2016, a real estate agent must hold a registration certificate from the state RERA authority before operating, and the certificate is valid for five years. Registered agents also have obligations under Section 10, including maintaining books of account and records as prescribed in the state rules (registration certificates commonly cite Rule 14). In practice this means transaction and account records must be kept organised and retrievable, which is a backup and access-control question as much as a filing one. Requirements vary by state, so check your state authority's rules.
DPDP Act 2023: you hold a lot of personal data
A CRM is a database of personal data: names, phone numbers, email addresses, budgets, family details and often identity documents. India's Digital Personal Data Protection Act, 2023 treats organisations that decide how personal data is processed as data fiduciaries. The DPDP Rules were notified on 13 November 2025, with the core obligations, including security safeguards and breach notification, taking effect on 13 May 2027, according to Hogan Lovells' summary. The rules refer to safeguards such as encryption, masking, access controls, monitoring, data backups and detection of unauthorised access, and to retaining logs for at least one year. On a breach, the Data Protection Board must be told without delay, followed by an updated report within 72 hours. The Act's penalties for failing to take reasonable security safeguards can reach ₹250 crore.
What this means for hardware: whether the CRM is on your own server or a vendor's cloud, you remain responsible for safeguards. A self-hosted server gives you direct control over disk encryption, user access, log retention and backups, but it also makes you responsible for configuring them. Self-hosting is a way to control the data, not a legal requirement. Our secure document server guide for law firms covers the same access-control and encryption design for confidential client files.
Self-Hosted Server, Cloud or Colocation?
There is no single right answer, and a self-hosted server is not always the best fit.
| Option | Works well when | Watch out for |
|---|---|---|
| Subscription CRM (SaaS) | Small team, standard sales process, no one to manage IT | Per-user fees grow with headcount; export and data control depend on the vendor |
| Rented cloud VM / VPS | Public listing site, variable traffic, no office hardware | Monthly cost continues; large media storage and egress can add up |
| Own server in the office | Many users, large media archive, custom CRM, wish to control data and avoid recurring per-user fees | You need power backup, backups and someone to maintain it |
| Own server in colocation | You want your hardware but not the office power and internet risk | Rack rental and travel for hands-on work |
Many agencies sensibly split the workload: the public listing website on a hosted platform where bursts of traffic are someone else's problem, and the private CRM, documents and backups on a server they control. Our on-premise vs colocation vs cloud guide walks through the cost and control comparison, and the how to choose a server for business guide helps you decide whether you need one at all.
Designing the Server: A Practical Layout
One box, several isolated services
Rather than buying a separate machine for every system, many offices run the CRM, the web application, the file share and the accounts software as separate virtual machines on one host using Proxmox or VMware. If the CRM needs an upgrade or breaks, the other services keep running, and you can snapshot a VM before changing it. We cover the approach in our office virtualization guide.
Memory
CRM databases and PHP or Python application workers benefit from having data cached in RAM, and silent memory errors on a machine that runs for months can corrupt records. All ProStation tiers use ECC DDR4 memory; see ECC vs non-ECC RAM for why that matters for a database.
Network
For a single office, standard Gigabit Ethernet is usually enough for CRM traffic. Faster links matter when many people open large media files from the server at once or when you back up hundreds of gigabytes over the network; see 1GbE vs 10GbE vs 25GbE. For branch offices, plan a secure VPN or a private link back to the head office, and test it before go-live.
Power and uptime
A lead that arrives during a power cut is a lead you may not see. A properly sized UPS rides through short outages and lets the server shut down cleanly during long ones; our UPS sizing guide shows how to calculate it, and the dual-PSU guide explains when a redundant power supply is worth the extra cost. To put a rupee figure on downtime for your own office, use the method in the cost of server downtime.
Backups: the part agencies skip
A practical baseline is the widely used 3-2-1 rule: three copies of the data, on two different kinds of storage, with one copy off-site. For an agency that means the live server, a local backup disk or NAS, and an encrypted copy outside the office. Test a restore at least once; an untested backup is only a hope. This also supports the DPDP expectation of data backups and the RERA expectation that records stay available.
Sizing Examples by Agency Type
ProStation has not published CRM or portal benchmarks, so the table below is planning guidance built from the workload logic above. Each row maps to the real Starter, Pro and Ultra tiers, and the exact configuration is confirmed in consulting.
| Agency profile | Typical workload | Starting point |
|---|---|---|
| Small brokerage, 5–20 users, one office | CRM, file share, accounts, modest photo archive | Starter tier (Intel Xeon E, 16–64GB ECC DDR4, 1TB NVMe) plus extra drives for media and a backup disk |
| Growing firm or builder's sales office, 20–100 users, 2–5 branches | CRM, listing site, large media archive, several VMs | Pro tier (Intel Xeon Scalable, 64–256GB ECC DDR4, 2TB NVMe plus HDD options) with RAID, UPS and an off-site backup |
| Large developer or multi-city network | Many branches, high-resolution media, internal analytics | Pro tier as the base, possibly two servers (production and backup/standby); consult before specifying more |
The Ultra tier is built for AI training, rendering and heavy compute, which a typical real estate workload does not need. We would not recommend it here, and we will say so in consulting. The Starter and Pro tiers list Ubuntu and Windows Server (Starter) and Ubuntu, Windows, VMware and Proxmox (Pro) as operating-system options, which covers the common CRM stacks.
When You Should Not Buy a Server
If you have a handful of agents, a standard sales process and nobody to look after IT, a subscription CRM and a managed website are likely to cost you less effort and less risk. A server also makes little sense if you cannot arrange power backup and a tested backup routine, because an unmaintained server is a bigger risk than a vendor's cloud. The point at which an owned server starts to pay off is typically many users, a large private media and document archive, a custom or self-hosted CRM, or a strong preference to control where customer data lives. If you are comparing buying new with other routes, see new vs refurbished servers and custom-built vs off-the-shelf.
Why Choose ProStation Systems for an Agency Server
ProStation Systems builds brand-new custom tower servers in India, specified from your real workload instead of a fixed catalogue. For a real estate agency, that means:
- Right-sized, not oversized. Free pre-buy consulting starts from your user count, CRM choice and media volume, and includes telling you when a cheaper option fits better. Use our pre-order checklist to prepare.
- Reliability by default. ECC memory on every tier, 80 PLUS Gold or Platinum power supplies, and a redundant PSU option.
- Tested before it ships. A 48-hour burn-in, delivery in about four working days and the operating system pre-installed.
- Built around your storage plan. Choose NVMe for the database and drive bays for media and backups in the configurator.
- Support where you work. A 1-year warranty with extended warranty available (see the warranty page), on-site engineer support in six cities, and pan-India delivery; see where we deliver.
If you are a small office the small business use case and small business server guide apply directly, and the storage and backup use case covers the media archive. For wider context see our enterprises and SMB industry page, and our e-commerce traffic-spike guide if your listing site expects sudden campaign traffic. Not sure about the price range? See custom server cost in India.
Frequently Asked Questions
Q1. What server specification does a real estate CRM need?
It depends on users, records and attachments, and most CRM vendors publish software requirements rather than a hardware minimum. EspoCRM, for example, lists PHP 8.3–8.5 and MySQL, MariaDB or PostgreSQL. A small agency typically needs a modest server with ECC memory, NVMe for the database, extra disks for media and a backup; larger multi-branch firms need more memory and isolated virtual machines.
Q2. Should a real estate agency host its CRM on its own server or in the cloud?
Either can work. A subscription CRM suits small teams without IT staff; an owned server suits many users, large media archives or a self-hosted CRM and a wish to control data. Many agencies host the public listing website in the cloud and keep the private CRM and documents on their own server.
Q3. Does DPDP law require me to keep data on my own server?
Not as a general rule. The DPDP Act requires reasonable security safeguards and breach reporting wherever the data is hosted. The Rules, notified on 13 November 2025, bring the core obligations into force on 13 May 2027. Owning the server gives you control of encryption, access and backups, but you must configure them. Take legal advice for your situation.
Q4. How much storage does a property portal need?
It depends on listing count and media quality. As an illustration, 2,000 listings with 20 photos of 3 MB each is about 120 GB before videos, brochures and documents. Plan for growth with spare drive bays and keep a separate backup copy.
Q5. Is RAID enough to protect my property records?
No. RAID keeps the server running if a disk fails, but it does not protect against accidental deletion, ransomware or fire. Pair it with a tested backup that includes an off-site copy.
Q6. Can ProStation build a server for my real estate agency?
Yes. ProStation Systems builds brand-new custom servers, specified from your user count, CRM and storage needs through free consulting or the configurator. Every build includes a 1-year warranty, with extended warranty available.
Final Recommendation
Size an agency server by users, media volume and recovery needs, not by raw speed. Put the CRM database on NVMe, keep media on redundant storage, add a UPS, and treat tested off-site backups as part of the server, not an extra. Check the CRM vendor's requirements for the exact release you will run, and confirm RERA and DPDP obligations with a qualified adviser. If you would like a configuration specified for your agency, call ProStation Systems on +91 87962 44410, message us on WhatsApp, or contact us.
Sources: EspoCRM — server configuration; Hogan Lovells — India's DPDP Act 2023 brought into force; KPMG — DPDP Act 2023 overview; Mondaq — Registration of real estate agents under RERA.