Agencies
Every client's wall, none of your branding.
The hard part of running social feeds for a dozen clients has never been building them. It is getting access to their accounts without collecting passwords, and making sure nothing on the finished page says the name of a tool the client has never heard of.
Who this is for
Digital, marketing and web agencies building and maintaining sites for other people, the ones already fielding "can we get our Instagram on the homepage" on every third project, and currently solving it with a different plugin each time.
A good fit
- Agencies maintaining more than a handful of client sites at once
- Teams who need a client's account connected without holding the client's credentials
- Anyone billing for a deliverable that must not carry a third-party badge
- Web studios on Webflow, Shopify or WordPress who want one approach across all of them
Probably not for you if
- A single in-house marketing team with one brand. The standard plans are simpler and cheaper
- Agencies who need to resell the product itself under their own name; the badge comes off the feed, but this is not a reseller programme
The five problems that show up on every client project
None of them are about rendering posts. They are about access, ownership and what happens eleven months later when the person who built it has left.
- Asking a client for their Instagram password is a security problem you are creating for both of you
- A different widget plugin on every site means a different renewal, a different bug and a different support thread
- Your client's site carrying another company's badge is a conversation you should not have to have
- When a token expires on a site you built two years ago, the client finds out before you do
- Twelve sites means twelve places to check when a client says their feed looks wrong
Client work usually has a house style to respect rather than a mood to set, which is what the editorial layout is for. It stays quiet and lets the site around it stay loudest.
How agency work actually runs here
One workspace holds every client. Roles decide who can change what. Each client's feeds carry that client's branding, and no Vitraz badge appears on their finished site.
Send a connect link instead of asking for a password
A single-use link the client opens themselves. They authorise on the network's own screen, the account lands in your workspace, and you never see a credential. They can revoke it from the network whenever they like.
One workspace, roles per person
Owner, admin, editor and viewer, from two seats on Studio up to ten on Scale. Bring a freelancer in as an editor for a build, make them a viewer afterwards, remove them without touching the work they did.
Nothing reaches a client's site until someone approves it
Set a feed to manual review and every new post waits in a queue until someone on your team approves it, from a laptop or a phone. Posts collected from a hashtag always wait, whatever the setting. On client work that is the difference between catching a bad post internally and the client catching it.
No Vitraz badge on the finished feed
From Spark up the badge comes off, so the feed on a client's site carries their brand and nothing else. The embed script still loads from vitraz.io, which only shows in the page source.
See which client sites a feed is live on
Once an embed loads on a site, the feed shows as installed, with the domain it loaded on. You can confirm a client's launch went out without opening their site.
What happens when a client leaves, or a source breaks
Agency tooling is judged on the bad day, not the good one. Two situations decide whether this is a liability on a site you no longer touch every week.
- Sources report their own health, so an expired token surfaces as a warning in your workspace rather than as a client email about a blank section
- Posts already collected keep displaying while a source is reconnected, a broken connection never blanks a live client page
- Removing a team member leaves their feeds, sources and moderation history intact under the workspace
- A client taking their site elsewhere takes an embed snippet that stops resolving; there is no hostage-taking here, but there is also no export of their posts to a competitor's format
- A plan's source limit counts connected accounts, so a client with six networks costs the same as six clients with one
Agencies questions, answered
Yes, and it is the intended path. You send a single-use connect link, they authorise on the network's own screen, and the account appears in your workspace. You never see a credential, and they can revoke access from the network at any time without going through you.
Yes, from Spark up: the badge comes off the feed, so nothing a visitor sees names Vitraz. The embed script still loads from vitraz.io, which shows only in the page source; there is no custom-domain serving.
It is bounded by feeds and sources rather than by a client count, so the shape of your book matters more than the size. A client with one Instagram feed and one connected account consumes one of each, and the embed itself goes on as many pages as you like. The pricing page lists the limits per plan.
Yes. Owner, admin, editor and viewer, invited by email and changed later without disruption. Admins manage the team and billing, editors connect sources and build feeds, and viewers can see the feeds without changing them.
No, and you should not. One workspace holding every client is what makes the health warnings and the team roles worth having. Separate accounts would give you separate bills and no overview.
Keep reading
See it with your own content.
Connect one source on the free plan and the whole editor works against your posts before you publish anything.
Start free