Six clients. Six Instagram accounts, five TikToks, four LinkedIns. One laptop, one browser, and a small pause every time you switch — because you are not certain what it looks like from the platform's side, and neither is anybody else.
Before anything else: if what you actually need is twenty accounts that read as twenty unrelated strangers, stop here. NOISEY will not do that, this post will not help, and it is better that you find out now than three weeks in.
What the internet tells you to do
Search any version of this question and the answer is consistent: an antidetect browser, one profile per client, a residential proxy attached to each, timezone and locale set to match. It is not a fringe recommendation — the category is large, well funded, and buys the top of every one of these search results.
It is also a coherent answer to a real problem, and this post is not going to pretend otherwise. The problem it solves is resemblance: those tools exist so that separate sessions do not look related.
Why NOISEY doesn't do that
Because if your accounts genuinely belong to different people, you do not have a resemblance problem to solve.
Six clients' accounts are already six unrelated accounts. Six different people registered them. They are about six different businesses, they answer to six different owners, and one of them can ask for theirs back on Friday. Nothing is being combined, so there is nothing to disguise. The thing being managed is not an appearance, it is a set of relationships.
There is a commercial reason too, and it is the one worth taking seriously. A tool whose entire value is that a platform cannot tell what you are doing is a tool whose value ends the day the platform can. You are not buying infrastructure; you are renting a position in an argument you do not control, against an opponent who ships every two weeks. That is a bad thing to build a client roster on.
The alternative is boring: one phone per client
A physical handset per client. The client's own account, signed in once, on a device that stays theirs. Real app, real login, your own office connection. Nothing is spoofed because nothing needs to be.
It is the same shape as the answer to “how do I make a fake ID look real”. Get a real one.
One phone per client, not per account — that distinction is most of the cost difference. A client on LinkedIn and TikTok and Instagram is one handset with three apps on it, each signed into that client's own account. In NOISEY a profile is that person or business, carrying however many accounts they have, and the phone gets a name — Onyx, Ember, Indigo — so that “post to Onyx” routes and “post to the ninth SM-G986U” does not.
What it actually costs
This is where most posts on this subject go quiet. The device answer is not the cheap one, and pretending otherwise wastes your afternoon and our trial.
Itemised, without spin:
- A handset per client. A used Android that still runs current app versions. Cheap individually, not free at six.
- A powered hub and the desk it lives on. Phones drawing charge over USB are a power budget, not an afterthought.
- Setup time. Install the apps, get the client signed in, name the phone, write the brief. Perhaps twenty minutes, and it is manual on purpose.
- A Mac that is awake. Jobs queue on the server and dispatch when the desktop app connects; with the lid shut, nothing posts and jobs sit at queued until it comes back.
- A ceiling. The free plan registers 2 phones and the paid plan 10, at $29/month. That is ten clients, not a thousand accounts. If you need a thousand, we are not the product.
What you get back is a shorter list but a durable one. No proxy bill. No profiles to keep consistent. No arms race with a platform's engineering team, because you are not in one. And when a client leaves, you hand them a phone with their account already on it — which is a remarkably good way to end a relationship you might want back.
Whose account is it, actually
Nobody in this corner of the internet talks about consent, which is odd, because it is the part that decides whether any of this is defensible.
The account holder registered the account. The account holder grants access — ideally by signing in on the handset themselves, which has the useful property that they saw exactly what they were agreeing to. What you are operating is a client's account with the client's permission, on a device you can point at.
NOISEY's position on the rest of it is deliberately unflattering to us: you are responsible for what your automations post. We execute the routines you author, against your accounts, and we do not review or approve them. The platforms' rules apply to you directly. That is not a disclaimer bolted on — it follows from the fact that we never touch a phone. The servers store rules and media and hand jobs to your machine; there is no path from them to a screen, and per handset we keep an identifier, a model and a status, never contents (the full inventory is here).
Where the line is
NOISEY is the user's devices, the user's accounts, the user's connectivity. Concretely, that means:
- No identifier modification. Not IMEI, Android ID, MAC address, build properties or model strings. The phone reports what it is.
- No proxy rotation, and no routing of your traffic. If all six handsets sit on the same office wifi, then they do, and nothing in the product suggests otherwise.
- No account registration. Not one, not in bulk.
- The product never writes a persona. A profile's brief is a field you type into, describing a real person — “a personal trainer in Leeds, expertise in strength training”. There is no button that invents one, and the more the product is aimed at agencies the more that matters, not less.
The last one has a shape you can see in the schema, which is the part I would point at if you only believed one paragraph here.
A profile's brief and its content pillars are model-facing; its notes are not, and they are separate columns precisely so the schema is the thing that says which. The timezone is operational: a 9am post for a client in Lisbon lands at 9am in Lisbon. It is not attached to a session and it is not presented to anyone.
And there is no control anywhere for varying a voice across handsets, because there is nowhere in the data to put one. Different voices means different routines, written on purpose, by you. That knob only makes sense under the reading we reject, so it stays absent — and a feature we chose not to build is a more honest signal than anything we could say about the ones we did.
So: is this for you
If you run six to ten client accounts, hold their permission, and want a setup you can explain to a client in one sentence, this shape works and it keeps working. It is more expensive on day one and it does not scale past the number of phones on your desk. Those are the honest terms.
If your model needs twenty identities that look like strangers, we are genuinely the wrong product, and you already knew that from the third paragraph.
The mechanics of what happens after the phones are on the desk are elsewhere: a file lands in a folder and a phone posts it, or n8n keeps the deciding and hands over the last mile. The docs cover the rest.