One account for many clients: how agencies keep client work apart
· SyncYak team
If you build and maintain sites for a dozen clients, the tooling sprawl is familiar. One client has its own error tracker login, another has a tunnel tool tied to a developer's personal email, and nobody can say what the total monthly cost is. When a developer leaves, you hunt through accounts to revoke access.
This guide shows how to run all of it from one account while keeping each client's work separate. It covers naming, projects, seats and cost, using SyncYak's published limits.
Decide what "separate" means for you
Before you create anything, write down what has to be kept apart per client. For most agencies it is three things:
- The public address of the client's staging or demo app, so a link you send last month still works.
- The error stream from the client's production site, so an alert tells you which client broke.
- Who can see what, so a freelancer working on one client is not browsing every other client's data.
SyncYak gives you a unit for the first two: a reserved subdomain per client for Tunnel, and a project per client for Cloud Logging. Access is handled with team seats on the one account.
Give each client a reserved name
A random tunnel address changes every time you restart. That is fine for a quick test and bad for a client demo, a webhook URL you registered with a payment provider, or an OAuth callback that must match exactly.
Reserve one name per client and use a predictable pattern, for example acme-staging and harbor-demo. Then start the tunnel with the same command each time:
syncyak http 3000
Each reserved name keeps its address across restarts, so the callback URL in the client's OAuth settings never goes stale. Tunnel also includes a request inspector, which is useful when a client asks why their webhook did not fire.
Plan for the numbers. Free includes 1 tunnel and a random subdomain. Hobby is $8 a month with 3 tunnels and 3 reserved subdomains. Pro is $20 a month with 10 of each. An extra reserved subdomain is $1 a month and an extra concurrent tunnel is $3 a month, so a roster of clients grows the bill in small steps.
One project per client in Cloud Logging
Cloud Logging is compatible with the Rollbar SDKs, so you keep the SDK you already use (JavaScript, Python, Ruby, PHP or Laravel) and change the endpoint. Create one project per client site and put that project's access token in that client's deploy configuration.
That gives you three practical benefits:
- Grouped errors per client. A noisy plugin on one site does not bury the real problem on another.
- Slack alerts per project. Send each client's alerts to a channel named after the client, so whoever is on call sees the client name before they open anything.
- Counts per client. You can see which client generates the most events and have an informed conversation about it.
The limits by plan, from the pricing page: Free gives 1 project and 10,000 events a month. Hobby is $9 a month with 5 projects and 100,000 events. Pro is $29 a month with 25 projects and 500,000 events, plus snooze, which is handy for a known issue you have agreed to fix next sprint. Business is $99 a month with unlimited projects. An extra project is $2 a month if you only need a few more.
If one client has a traffic spike, you can allow on-demand events past the plan allowance up to a cap you set, instead of losing errors or being surprised by a bill.
Seats: give people only what they need
Team members besides the owner are counted as seats, and the highest tier you hold on any product sets the allowance: 2 on Free, 5 on Hobby, 10 on Pro and 25 on Business. An extra member is $5 a month.
A simple policy that works for small agencies:
- Developers who work across clients get a seat.
- Freelancers on a single client are added for the length of the engagement and removed when it ends.
- Client staff do not need a seat. Send them the tunnel link or the Slack alert, not a login.
Revoking access on the last day of a contract is easier to remember when everyone is on one account rather than scattered across tools.
A worked example: eight clients, four developers
Suppose you maintain eight client sites and four developers share the work.
| Need | What you pick | Monthly cost |
|---|---|---|
| 8 reserved staging names, 8 tunnels | Tunnel Pro (10 tunnels, 10 reserved) | $20 |
| 8 error projects | Cloud Logging Pro (25 projects) | $29 |
| 4 developers plus owner | Pro seats cover 10 | included |
That is $49 a month for the eight clients, with room to grow to 10 reserved names and 25 projects before you pay for add-ons. Confirm current prices on the pricing page before you quote anyone, since plans can change.
If your roster is smaller, Hobby covers 3 reserved names and 5 projects for $8 and $9 a month. Start there and move up when you add the fourth client.
Naming conventions that save time later
Small habits pay off when you have twenty clients:
- Use the same slug everywhere: the tunnel name, the project name and the Slack channel all say
acme. - Add the environment to the name:
acme-staging,acme-prod. - Put the project token in the client's secrets store, never in the repository.
- Keep a one-page index (a Google Sheet works) listing client, tunnel name, project and owner. Review it when a developer joins or leaves.
How SyncYak helps
Tunnel, Cloud Logging, Mail, Parse and CRM share one account, one team and one bill, so the agency setup above does not need a separate tool for each job. Read how it fits for platforms and agencies, see the tunnel for agencies and error tracking for agencies pages, and compare plans on the pricing page.
Next step
Create a free account at SyncYak, reserve a name for your first client's staging app, and point one project's Rollbar endpoint at Cloud Logging. Add the other clients one at a time.