Audience
Agencies — client isolation, templates, and delivery
Agencies waste hours rebuilding context per client. Vekra keeps each client’s brief, brand, site, and marketing on an isolated project. White-label custom domains are reserved, not live. No invented time-saved claims.
One client, one project
Create the client in the agency workspace and attach exactly one Vekra project. Another client cannot open it. The client portal, when you use it, only shows that client’s work. Do not reuse one project as a junk drawer for three brands.
Roles and shared assets
Owner, Admin, Member, and Viewer are enforced on the server. Share a file with one named client or keep it team-only. Portal visitors are not team members. Permissions are not a UI-only hint.
Delivery chain you can explain on a call
Brief and plan → brand kit → website pack the client hosts → marketing drafts they approve → export. Credits use the same ledger as the rest of Vekra; agency limits are soft ceilings, not a second wallet. If you need the signup-oriented story, use the agencies conversion landing.
Templates without cloning junk
Save a project as a template when the brief pattern repeats. Customize the next client instead of pasting last month’s invented testimonials. Workspace templates live behind sign-in; the public /templates page is a marketing index of starters.
Outcomes
- Client projects that cannot see each other
- Roles and asset sharing with server checks
- Exports for approval — not live publish on the client’s domain
FAQ
Is agency white-label live?
Custom-domain white-label is reserved, not live. Do not sell it as a shipped feature.
Where do I sign up as a team?
Start Building on the Business plan from /solutions/agencies, or Talk to Sales via Contact.
How is this different from the agency landing?
/solutions/agencies is the conversion page. This page is the operating model: isolation, roles, delivery.