How it works
Six things we can point at in the code
Separated at the data layer
Every query is scoped to your organisation by the database client itself, not by each screen remembering to add a filter. A developer who forgets a where-clause gets no rows rather than somebody else's rows. That is the difference between a convention and a guarantee.
Roles enforced on the server
The sidebar hides what a role cannot use, but hiding is not security. A URL typed directly is checked the same way a click is, on the server, on every request.
Hosted in India
Microsoft Azure, South India region. Your records and your customers' details stay in the country they were collected in.
One active session
Signing in on a second device ends the first. Shared logins make an activity log meaningless, so they are made impractical rather than merely discouraged.
Leaving does not take data with it
Suspend an account and it cannot sign in, stops being billed, and everything it worked on stays exactly where it is. No export happens on the way out the door.
Your data leaves whenever you ask
Leads, listings and reports export as CSV on demand. Software you cannot leave is software that has stopped needing to be good, and we would rather stay useful than become difficult to remove.
The bug we went looking for
Early on, BluPlots let agents sign themselves up from a public page. The code filed each applicant into the first organisation it found in the database. With one brokerage on the system this looked like it worked. With two, it would have handed a stranger a login to somebody else’s customer list.
We removed public sign-up entirely. People now join by invitation from an administrator, and the link creates that account inside that organisation and nowhere else. Then we checked the rest of the product the same way: a fresh organisation was created and every admin screen was opened to confirm it saw zero records and no names belonging to anybody else.
We mention it because a security page that lists only successes is not telling you how the software is built. It is telling you what the marketing team was comfortable with.
Being straight about it
What we have not done yet
Things worth knowing before you decide, which most vendors would leave for you to discover.
No third-party security audit
The product has not been penetration tested by an outside firm. When it is, this page will say who did it and when.
No SOC 2 or ISO certification
We do not hold either. If your procurement process requires one, we are not the right fit yet, and it is better to know that now.
No two-factor authentication yet
Sign-in is email and password with one active session. Two-factor is on the list and is not there today.
Questions
Data and security
Who can see our data?
Only your organisation. Every database query is scoped to your tenant at the data layer rather than by each screen remembering to filter, so a missed filter cannot leak another brokerage's records.
Where is it hosted?
Microsoft Azure, in the South India region. Your data stays in India.
Can we get our data out?
Yes, whenever you want, as CSV. Leads, listings and reports all export. Software you cannot leave is software that has stopped needing to be good.
What happens when someone leaves the company?
Suspend them and they cannot sign in, their seat stops being billed, and everything they worked on stays where it is. Nothing walks out with the person.
Can two people share a login?
Not usefully. One session is active at a time, so a second sign-in ends the first. That is deliberate: shared logins make an activity log meaningless.
Do you look at our data?
Not routinely, and not without asking. If you report a problem we may need to look at the specific record involved to fix it, and we will say so.
Questions we have not answered here?
Ask them before you commit rather than after. We would rather lose a sale to an honest answer than win one and disappoint you in month two.