You want a site with your own design, on your own domain and your own server, and when you ask for a quote you end up with two paths that do not convince you: a template where the design is not yours, or a build from scratch that starts in weeks and keeps costing every time something changes.
And there is one part neither of them solves on its own: making the site show your portfolio up to date. If the properties live in one place and the site in another, somebody has to copy them across, and that somebody is you.
So we published ours. It is a complete real estate site, open, that reads your properties straight from your Mapaprop account — and it is the same one we use to show the API working.
See it running
express.mapaprop.com is the site actually running, with real properties. It is not a mock-up or a video: it is what gets deployed when you download it.
What it brings
A whole site, not a loose sample:
- Home with cover, search, featured properties, developments, areas and your branches.
- Search with filters by operation, type, area and price, and pagination.
- Property page with gallery, floor plans, videos, map and inquiry form.
- Developments, with their units.
- Blog, contact and seller capture with attachments.
- Spanish, English and Portuguese, with a selector.
Everything reads from your account: you load the property once in Mapaprop and the site takes it from there — the photos, the price, the area and the status. If you sell it, the site reflects that.
You download it and it is yours
It is open source, under the MIT license: download it, change it and publish it however you want. It is written in HTML and JavaScript, with no framework and no build step, so your designer opens it, edits it and sees the change. You do not need a team to touch it.
Your copy is yours and nobody touches it: the site you published stays as you published it, and we do not push changes into it. What we keep moving is the repository: we keep it up to date with every change in the API and we keep adding improvements, and whenever you want to take one, it is there to download. If you are missing a filter, a block or a language, you ask for it there and we look into it; if you already solved it, you send us your change.
Try it with no account and no token
It comes with a test mode on sample data. Your designer or your developer opens it, works on the design and sees the whole site running without an account, without a token and without asking you for anything. Only when you like how it looks do you paste your token in.
Where you publish it
Wherever you want, and there are two paths.
One click on Vercel. The button in the repository builds the site in your own account and asks you for the token during the process. It is the shortest path: there is nothing to configure.
On your own server. It is a Node server with no dependencies and it starts up like any other application. Netlify, Cloudflare and AWS work too, with a small adjustment to the function that holds the token — and we will be adding ready-to-use options.
The hosting is yours, and that is why the decision of where it lives is yours too.
The token stays on the server side, never in the browser: it is the most important architectural decision in the project and it is explained in the manual, because it is the one worth understanding before changing anything.
Inquiries come back to your account
This is what makes it different from a site built outside: the form on every property page enters your Mapaprop Inbox as a lead. You assign it to an agent, you follow up on it, it stays in your reports and it triggers your automations. The site is yours and it lives wherever you want, but the customer who gets in touch enters your CRM just like always.
The same goes for the seller capture form: the owner who leaves you their property to sell or rent arrives with their photos and their documents, in your account.
Which plan includes it
The site is free and open. What you need is the API Token, included from Mapaprop Pro+: you activate it yourself with one click in Settings > API Token, without asking anyone for permission.
Where to go next
- The reference client manual — from zero to deployed, the map of the code and why the token lives on the server side
- The code on GitHub
- Express API: every method
- How to activate your API Token