Six stages. Your crew touches one of them. FLAY runs the other five, every 20 minutes, day and night.
Captains and deckhands open FLAY on their phone and upload whatever they shot. No sorting, no renaming, no editing. Twenty photos from the dock at 4 PM is a normal day.
Within minutes, AI vision opens each upload and works out what's actually in it. Not "a fish" but which species, who's in the shot, what the moment is, and whether it's worth showing anyone.
Anything scoring 6 or better goes into your library. Anything below 6 is deleted, from the database and from storage, before a human ever scrolls past it.
A second pass writes the caption: a hook, a line that sells, your phone number and booking link. Grounded in the photo and in your own info sheet: real boats, real prices, real seasons.
More on the writing rules on the Copywriting page.
Finished content enters the pool. The planner fills a calendar days ahead, one slot at a time, following two laws: a piece posts once per channel, ever, and a piece appears on one channel per day, so your pages never look like they're copying each other.
Full detail on the Scheduling page.
Every 20 minutes FLAY checks the calendar. When a slot is due, it publishes one post, one channel, one tick. Never a burst, because platforms punish bursts.
Not on the same channel. Each piece of content posts once per channel, ever, and on at most one channel per day. When the pool runs low, the calendar simply has fewer posts. It never recycles.
Captions are written from your info sheet (boats, prices, seasons, contact numbers) and from what's visible in the frame. You can edit any caption before it fires, and any correction to the sheet applies to everything written after it.
Analysis runs on a drip a few minutes after upload. Once a photo is verified and captioned it's in the pool, and the next planner run puts it on the calendar. Typically same day in, posting within a few days, depending on how full your calendar already is.
No. A captain sees only the boats assigned to them. Fleet owners see their whole fleet. Every tenant is isolated at the database level. See the Security page.
A channel that fails three posts in a row pauses itself for a cooldown and retries once. If the publishing engine itself stops responding, FLAY stops firing entirely and holds the calendar until it's back, so nothing is wasted and nothing double-posts.
See the calendar and the pool in action on the Screenshots page, or start a trial and pour your first batch in.
Start Free Trial