Agencies and software platforms can put QuickCasa behind their own brand. Manage every client account from one login, repaint the portal in your colours and logo, or build straight onto the API. Take it as far as you want.
They stack. Start by running accounts for clients, brand the portal when you are ready, and move to the API if you need your own front end.
Work inside every client account from a single login, switching between them as you go.
Put your logo and colours on the portal so your clients see your brand, not ours.
Use QuickCasa as the engine under your own product, through a REST API and an MCP server.
Your team gets added to each client's QuickCasa company and switches between them from the sidebar. No second password, no separate browser profile, no signing out to check on someone else.
Each client stays the owner of their own account and their own data. You work inside it with whatever permissions they grant your team, so the arrangement stays clear on both sides.
Build a theme and the portal stops looking like QuickCasa. One theme sets the page background, the sidebar, the top bar, cards and tables, buttons, links and form fields together, so nothing is left half-branded.
Text colours are worked out automatically against whatever surface they sit on, which means a theme stays readable without anyone hand-checking contrast.
If you are putting QuickCasa underneath your own product, work against it directly. Access is through a scoped API key issued to the company, and the key is what identifies you, so an integration can only ever touch its own data.
Create and update property inventory programmatically at api.quickcasa.ai/v1, so listings in your system land in QuickCasa without anyone retyping them.
Point Claude Code, Cursor or any MCP client at api.quickcasa.ai/v1/mcp to build and publish websites, manage CMS content, and work with inventory and leads in natural language.
POST a contact to a cadence URL to enrol them in a follow-up sequence, or fire a data-integration flow from your own system when something changes.
The three paths above are things you can do in the product today. A few deeper pieces we handle with partners case by case, because they need the right plan and a bit of setup on our side.
That is up to how far you take the branding. With your own theme applied as the company default, the portal carries your logo, your icon and your colours for every user in that account. The underlying product is still QuickCasa, and we are not going to pretend otherwise, but what your clients look at every day is your brand.
Yes. Once your user belongs to more than one company, an account switcher appears in the sidebar and you move between clients without signing out. Permissions are set per company, so each client controls what your team can reach in their account.
The client does. You operate inside their company with the access they grant you. If the relationship ends, the account and everything in it stays with them.
Yes. Any theme can be exported as a JSON file and imported into another company, where it becomes a new theme owned by that account. Build the look once and roll it out to the rest.
Keys are issued per company and scoped to what the integration needs. For the website and CMS toolset there is a Connect AI button in the website editor that hands you a key and the setup snippets. For the Resident API and anything deeper, talk to us first so we can get you on the right plan.
No. The affiliate program pays you for introducing property managers to QuickCasa. White labelling is for running QuickCasa yourself, under your own brand, for clients you already serve. Plenty of partners do both.