Why Ember exists

The problem it was built for

A brand-new social account has no history. When it posts for the first time, the recommendation system has nothing to go on: no watch patterns, no likes, no follows, nothing that says what this account is interested in or who it should be shown to. Clippers feel this as the first few posts landing flat regardless of how good the clip is.

The common workaround is to scroll the account manually for a week before posting. That works, and it is unbelievably tedious — which is exactly the kind of job worth automating.

The approach

Ember spends one to five hours behaving like a real new user on the account: watching videos in a niche you choose, liking some of them, following a few relevant creators, occasionally leaving a comment. It runs from a cloud phone you control, optionally behind your own proxy, and it paces activity across the run rather than firing everything at once.

Then it stops. Ember does not post your content for you. The point is to hand you an account that already reads as a real person with real interests, and let you take it from there.

What it deliberately does not do

• It never asks for your platform password. You sign into the cloud phone yourself. There is no field in Ember for a TikTok password because there is no reason for one to exist.
• It does not buy followers or fake engagement. Everything it does is ordinary consumption activity on the account you own.
• It does not auto-post comments by default. Drafts go to a queue for you to approve, because a bad comment on a warming account is worse than no comment.
• It does not pretend the risk is zero. Automating a social account can get it restricted or banned. Ember is built to reduce the signals that cause that; it cannot eliminate them, and any tool claiming otherwise is selling you something.

Who builds it

Ember is built and run by one person, which shapes the product in ways worth being upfront about: development moves in bursts, support is a single inbox rather than a team, and features get built when they are genuinely ready rather than announced on a roadmap.

How it started

Ember began as a chore. Spinning up a new clip account meant sitting with a phone for an evening, scrolling one niche, liking things I didn't care about, so that the account would look like a person before it looked like a publisher. It worked. It was also a genuinely stupid way to spend an evening — the definition of a job that should be automated.

The first version was a script. Scripts are where most of these tools stop, and it is exactly where the interesting problems start, because a script that does the job as fast as it can is a script that gets accounts banned. Every real decision after that point was about slowing the thing down and making it legible.

That is where the product actually took shape, and the constraints it settled on are the ones still in the code:

• Hours, not minutes. A run is paced across one to five hours in half-hour steps, ramping rather than starting flat out, because a burst of activity from a minutes-old account is the exact signal the warm-up exists to avoid producing.
• Cloud phones, not emulators. Emulators are free and detectable. Paying for a real Android instance is the boring, expensive, correct answer.
• Comments get approved by a human. Auto-posting was the first feature built and the first one turned off by default. A bad comment on a warming account is worse than no comment.
• Nothing runs on a real account by accident. There is a hard gate in the dispatch path that refuses to send activity to any account not explicitly marked as a test account. It has stayed in place through every version.

The thing that took longest to accept was that the honest version of this product is less impressive than the dishonest one. It would be easy to promise view counts. Ember doesn't, because warm-up changes who sees your first post — not whether the post is any good, and not whether the platform decides to restrict you anyway.

Get in touch

Questions, bug reports and feature requests all go to the same place: business@emberapp.site. If you want to see how it works first, the how it works section walks through a run, and the blog goes deeper on the reasoning.