About BRoller

A small product from a small company, built because we needed it ourselves.

Why it exists

We ran social accounts before we built tooling for them. The work that ate the day was never the ideas. It was the fifteen minutes per post spent resizing images, retyping the same caption structure, checking that nothing sat under the share button, then opening a separate analytics screen to find out whether any of it worked.

BRoller collapses that into one place: build the deck, write the copy, send it to your drafts, see the numbers come back. Everything else we deliberately left out.

Why it stops at the draft

BRoller can put a finished post into your TikTok drafts. It cannot publish it. That is a choice, and we get asked about it often enough to explain it here.

Automated publishing sounds like time saved until the day it publishes the wrong deck, or the right deck with last week's caption, to an audience of a hundred thousand people. The failure is public, permanent and yours. Thirty seconds in the TikTok app before you press post is the cheapest insurance in the whole workflow, so we made it mandatory.

How we handle your account

Three commitments, and they are reflected in the code, not only in the marketing:

• Least access. BRoller asks TikTok for the narrowest set of permissions that makes the features work, and each one is explained on screen before you approve it.
• No publishing. BRoller holds no permission that lets it post to your profile directly.
• No data sale. We have no advertising product and no data brokerage. Your account data is used to run BRoller for you and for nothing else.

The company

BRoller is a product of LIMED CONSULTING LLC. We build and maintain a small number of tools rather than a large number, which is why support is answered by the people who wrote the thing you are asking about.

Where it is going

The near term list is short and public: better handling of video frames as source material, saved looks shared across a team, and a weekly digest of your own numbers by email. Shipped work is recorded in the changelog.