luminarforge.
Try it free
The dispatch desk — publishing & returns

LinkedIn ships itself. The rest ship honest.

Approved posts publish straight to LinkedIn on our own schedule — no browser automation, no Zapier. For Instagram, Facebook and X we’d rather show you the manual steps than fake a connector. They’re printed below.

Start free — 5,000 credits Read the manual path ↓

Publishing on every plan · every connection scoped to one client workspace

Fig. 1 — the channel matrix, as it stands today Updated when reality changes — not before
ChannelDispatchWhat that means
LinkedInPersonal profiles Native Publish now or schedule — the dispatcher posts it for you. OAuth per client workspace, tokens encrypted at rest.
LinkedInCompany pages Available Client company pages publish through a third-party publishing partner — not our own LinkedIn app. LinkedIn refused us direct company-page access, so we took the route that works.
Instagram · FacebookMeta Manual — formatted Natively-formatted drafts, one click to copy, you post in the app. Native connectors are on the roadmap behind Meta’s app review.
XTwitter Manual — formatted Drafts truncated to the real 280 characters including hashtags — what you copy is what fits.
Native = the dispatcher posts it · manual = formatted copy, you post it No browser automation · no Zapier · ever
The dispatcher — engineering datasheet

Boring, reliable machinery. On purpose.

Scheduled posts are dispatched by a Postgres cron worker that wakes every minute, claims due posts atomically — so a post can never double-fire — and hands each one to LinkedIn. A profile connected with LinkedIn sign-in goes out on our own LinkedIn app; anything connected through the partner — every company page, every carousel — goes out through them. The queue is ours either way.

If a dispatch fails, the card says failed, and why. Transient errors retry on the next run; permanent ones — an expired connection, a policy rejection — stop and tell you the reason. No silent success theatre.

Schedule it and close the laptop. That’s the feature.

Dispatch spec — LinkedInAs implemented
WorkerPostgres cron, every minute — no third-party queue in the loop
ClaimingAtomic — status-guarded update; a due post is dispatched exactly once
Failure handlingTransient errors retry next run; permanent errors mark the card failed with the reason recorded
TokensAES-256-GCM encrypted at rest, decrypted only in memory; auto-refresh with a 5-minute buffer
IsolationEvery connection is scoped to one client workspace — enforced on the server, never in the browser
Guard rail10 publishes per hour per user — a fat-finger brake, not a quota
The manual path — said out loud

Here is exactly what manual publish looks like.

Most tools bury this. We’d rather print it: until Instagram’s connector clears Meta’s review, publishing there is a copy-paste with the formatting already done. About a minute per post — and you should know that before you buy, not after.

A fake connector costs you a client. A printed manual step costs you a minute.

Dispatch ticket — Instagram, manual~1 minute
1

Open the card’s Instagram tab — the preview shows the post as that platform expects it.

2

Click “Copy for Instagram” — the caption lands on your clipboard with hashtags already tucked below the fold . . . Instagram-style.

3

Save the artwork from the preview — it was generated at the post’s real shape, so there’s nothing to crop.

4

Paste and post in Instagram’s own composer. Done — mark the card published so the calendar stays true.

Same ticket for Facebook · X drafts arrive pre-cut to 280 characters · native connectors replace this ticket when they clear review
The returns desk — what comes back

What comes back, by connection.

Published LinkedIn posts report back on a schedule that respects the platform’s API budget instead of burning it: fresh posts sync daily; older posts weekly; after thirty days they rest.

Not real-time. Not pretending to be.

Each sync updates the card’s current numbers and keeps a dated record, so the performance page can draw how a post grew rather than only where it landed.

Personal-profile posts carry likes, comments and shares. Company pages add impressions and reach. Clicks are not on either list — LinkedIn reports those only through the access we were refused, so we don’t print a number we cannot produce. We report what the platform reports.

Returns scheduleAs implemented
Posts under 7 days oldSynced daily
Posts 7–30 days oldSynced weekly
Posts over 30 daysAt rest
API budgetQuota-aware — capped per run
Current figures, plus a dated record — each sync updates the card and keeps the day’s numbers
Said plainly — how we keep this honest
On company pages

Posting to a client’s company page works today — but not on our own LinkedIn app. We applied for direct company-page access and were refused, permanently, so company pages and carousels go out through an third-party publishing partner instead. Same result for you, different plumbing, and we would rather say so than imply we built all of it ourselves.

On analytics

You get what LinkedIn actually returns for the connection you made, on the schedule printed above — measured figures, never an invented score or an “engagement grade.” When the platform gives us more, you’ll get more.

The dispatch window is open

Schedule it. Close the laptop.

Start free with 5,000 credits — connect a client’s LinkedIn, approve a post, and let the dispatcher do the boring part. Roughly a fortnight of real production, on us.

Start with 5,000 free credits See the rate card

No card · No trial countdown · No per-client fees