Multi-brand workspaces
Separate contacts, campaigns, roles and credits for each product or client.

inHouze Marketing Engine · Developer Preview
Built for builders / 001Your marketing stack shouldn’t multiply every time you ship a product.
Run contacts, campaigns, content, automation, AI assistance, analytics and customer-facing growth experiences from one reusable layer—across your own products and client brands.
Built first to power inHouze products. Designed to become reusable infrastructure for other builders.
01 The problem
One engine. Multiple brands.
One source of marketing truth.
02 How the model works
Keep each brand’s data separate. Reuse the operating layer behind it.
Products & client brands
One reusable operating layer
Contacts + Audiences
Core engineCampaigns + Content
Core engineSocial + Email
Social now · email campaigns nextAutomations + AI
Core engineEvents + Attribution
Core engineCustomer-facing pages
PlannedOwned proof-of-concept brands. The same core engine, different products—not client testimonials.
03 The operating layer
A connected set of tools—not another silo. Here’s what’s working, and where we’re heading.
Separate contacts, campaigns, roles and credits for each product or client.
A shared contact timeline, tags and server-evaluated audience rules.
Plan campaigns, draft content and review it before publishing.
Publish approved content to LinkedIn profiles and Facebook Pages.
Public forms that put leads and their activity into the right workspace.
Follow up on forms, events and tags with transactional emails and team actions.
Brand-aware assistance and creation tools with human review before action.
Ingest product events through API keys or a browser tracking snippet.
Campaign UTM matching and channel reports. Multi-touch attribution is next.
Customer-facing campaign pages and branded portals on the same layer.
A reusable home for approved brand and campaign assets.
A modular integration direction, not a promise that every provider is connected.
04 Built for developers
Send behaviour into the engine. Give it brand context. Connect the customer journey without rebuilding a marketing stack for every app.
POST /api/public/v1/events{
"name": "signup_completed",
"properties": { "product": "your_app" },
"utm": { "utm_source": "launch" }
}Event ingestion is implemented; broader endpoints are expanding.
Workspace-scoped secret keys and write-only property keys.
Signed outgoing hooks for your own product workflows.
Track product behaviour through an endpoint or browser snippet.
Public form submission exists; a general developer API is next.
Packaged tools for embedding the engine in your apps.
A branded edition under your own client relationship.
05 Product direction
No public pricing yet. Editions are a product direction, not a promise of general availability.
Our own portfolio
The operating layer we use for our products and brands.
An isolated client workspace
A separate workspace, permissions and brand context for client work.
Multiple apps / products
Connect growth experiences across the products you build.
Your client relationship
Manage multiple brands with your own presentation and identity.
06 One campaign, one connected flow
The connected vision: from choosing an audience to understanding what worked.
07 Current vs next
This is an early-access product, not a finished catalogue of promises.
Present in the current engine. Developer access is opening gradually.
Planned or unfinished. No public release dates promised.
08 Early access
We’re opening the platform gradually to developers and studios who manage multiple products or client brands.
For builders looking for a reusable marketing operating layer—not another standalone newsletter tool.
Less stitching. More shipping.