RRevenue + pipelineActive
A secure client portal each client can shape, and none can break.
A client portal lives or dies on the boundary. Every client needs their own view of their own data, and no client should ever see, reach, or break anyone else's. ShapeKit starts from that line. You define what each client can access and change. They reshape the rest themselves, in plain language. The runtime keeps everyone inside their lane.
Security is the boundary, and the boundary is enforced
Most portals make you choose between locking everything down and opening things up. Lock it down and clients flood you with layout requests. Open it up and you risk exposing data across accounts. ShapeKit removes the trade by separating what is shapeable from what is fixed, and enforcing the difference at runtime, not in the UI.
Multi-tenant isolation by default. Each client's data is scoped to that client. Reshaping changes presentation only. A client cannot query past their own boundary, no matter how they arrange their view.
You set the access limits. You decide which fields, records, and actions each client can see and use. Those limits are server-side. A client's Shape request can only operate on what you have already permitted.
Customization cannot escalate access. Clients reorder, filter, hide, and rearrange. They never touch the data model, the business logic, or another client's records. The shape layer has no path to the things you locked.
Each client gets their own view, without duplicate apps
The usual way to give clients different views is to build a copy of the portal per client. That does not scale, and every base change has to be made in every copy. ShapeKit keeps one app and lets each client reshape it.
You build one portal
Define the data, the permissions, and what each client can change. One app, one source of truth, one thing to maintain.
Clients shape their own view
Each client hits Shape, describes the layout they want, and the AI rebuilds it. No ticket to you. No waiting on a release.
Versions stay in sync
Each client's shape is versioned. When you update the base portal, their view migrates forward instead of breaking.
Built for the people who run client work
Agencies, accountants, law firms, consultants, and any team that hands a portal to outside clients run into the same wall: clients want it their way, and you cannot give every one of them a developer. ShapeKit gives them self-service inside a boundary you control, so the customization queue stops landing on your team.
Give clients a portal they can shape, on a boundary you trust.
Build one secure portal. Let each client make it their own, without putting your data at risk.