Connect your social accounts

One click each. You approve on Facebook's / Google's own screen — we never see your password.

Point us at your storage (optional)

Your videos stay in your account — your free tier, your files. We just need to read them at posting time. Or skip this and paste public links.

Fill your content library

Add each video once, with a sentence describing it. That description is what the AI writes captions from — the better it is, the better the captions.

Run Autopilot

Pick 7, 30, 180 days. We take unposted videos, write a different caption for every platform, and fill your calendar.

Dashboard → Connected accounts → the platform card → Paste token.

Fill in the fields and hit Check & connect.

We call the platform right then to make sure the token works and can actually post — not just read. A bad token is rejected on the spot, with the platform's own error message. You'll never find out at 8pm because a post silently failed.

Create a free account at dash.cloudflare.com/sign-up.

Copy your Account ID — it's the long string in your dashboard URL: dash.cloudflare.com/<account-id>.

Go to R2 → Manage API Tokens → Create Account API token. Permission: Admin Read & Write.

It has to be Admin, not "Object" — we create the bucket for you, and only Admin can do that. Pick Object-level and the save will fail.

Copy the Access Key ID and Secret Access Key — the secret is shown once. Close the page without copying and you'll have to make a new token.

Paste the three values in Storage → Cloudflare R2 and hit save.

Just switched R2 on? Give it a couple of minutes. Cloudflare needs a moment to bring your account's storage endpoint online, and until it does the save fails with a connection error even though every value is correct.

On save we verify the key against Cloudflare (a bad key is rejected on the spot), create the bucket for you, and measure space already used so the full-storage warnings are accurate from day one. You never touch bucket settings.

In the AWS console, open S3 → Create bucket. Note the region (e.g. us-east-1).

Allow public reads on the bucket so Facebook/Instagram can fetch the files.

Open IAM → Users → create a user → attach a policy limited to this bucket only.

Don't use your root key. If it ever leaks, you want the damage limited to one bucket.

Create an access key for that user, then paste the key, secret, bucket, and region into Storage → Amazon S3.

Storage → Content library → Add video.

Fill in the title, the video URL, and — the important one — what's in it.

That description is the only thing the AI sees when writing your captions.

Pick how long you want covered: 1, 3, 7, 15, 30, 60, 90, or 180 days.

Set posts per day (1–5), tone, and which accounts.

The summary does the math for you: posts per day × days = videos needed. 3 a day for 30 days needs 90 videos. It compares that to your library and warns you before you run, so there are no surprises after the fact.

Hit Suggest my calendar.

We pick videos that have never been posted (oldest first), and the AI writes a caption for each one on each platform. Still nothing scheduled at this point.

Read the list. Untick anything you don't like, then Approve & schedule.

Only the ticked posts get scheduled — and they go out with the exact caption you just read. We don't re-write it behind your back.

Describe the video in one sentence.

Pick accounts, tone, language.

Write & schedule everything. Every platform gets its own caption, at its own best time.