AppsMorax PostPilot

All your publishing, one place

Available

Publishing everywhere, from one place

Eight networks, eight logins, eight formats, and a subscription that charged per connected account. Morax PostPilot took the whole thing over: it draws on what your site and your delivered galleries already hold, writes the posts, plans the campaign, and sends each piece out on the date you set. It publishes for two brands today, and the interesting engineering is not the posting — it is never posting the same thing twice.

Open to two brands. New accounts wait on platform app review, not on code.

The PostPilot dashboard in a light theme: a sidebar for the calendar, the feed, the queue and the media library, four counters for total content, posts due this week, drafts and connected networks, a list of upcoming publications with their network and status, and shortcut cards for content routines, the editorial calendar and the image bank.
Posts drawn from the same galleries the photographs are delivered from, queued for Instagram, LinkedIn, Pinterest and Facebook. Nothing goes out without passing the queue.

What this product does

  • Every network, one queue

    Instagram, Facebook, LinkedIn, Pinterest, TikTok, YouTube, WordPress and Ghost sit behind a single queue and a single calendar. Each platform is a folder implementing one contract, so adding the next one is a file rather than a project.

  • Written from what you already have

    Your site, your delivered galleries, your finished projects: the material for a post is work you have already done. Paste the URL of a gallery you just delivered and it comes back as a series of drafts, each already illustrated, each on a different angle, no photo used twice.

  • Campaigns, not one-off posts

    A campaign is a window, a cadence and a split across platforms: twenty posts over six weeks, two thirds Instagram, one third LinkedIn. The split is honoured exactly over the run rather than rounded week by week, and the platforms alternate instead of arriving in blocks.

In detail

  • A crash never posts twice

    Publishing runs as a state machine held in Postgres: one step per tick, the progress written down before each mutation. Kill the process mid-publish and the next tick finds out what actually happened instead of trying again. When the outcome genuinely cannot be known, the job stops and says so — it is never replayed on a silence.

  • Refused while you write, not in a log

    A carousel of eleven images, a caption over the limit, a YouTube title with an angle bracket in it: the rules are known in advance, so they are checked while you write and enforced when the post is queued.

  • Video sent in pieces

    TikTok and YouTube get one byte range per tick, read straight from where the file already lives. The function never holds the film, and an interrupted upload resumes from what the platform says it received.

  • Accounts you can actually see

    One card per connected account, with a computed verdict rather than a stored label: expiry, permissions granted against permissions required, and whether it will still publish tomorrow. Tokens are encrypted; a connection that needs a human says so before anything is sent.

  • An app, not a module of the hub

    Morax PostPilot lives on its own surface, under its own domain, with its own database and billing. The hub opens it, it doesn't absorb it.

Who it is for

A shoot you just delivered
The gallery URL is the input. What comes back is a run of illustrated drafts, spread over the cadence you chose, waiting to be read rather than written.
A run of teaching videos
One subject per piece, planned across the weeks and published on its date, with the upload handled a chunk at a time so a long video is not a special case.
Planning an editorial month
The calendar shows how the slots spread over the month, which platform each one lands on, and where the gaps are.

See the queue

The queue, the calendar and the connections open behind a login — this is a working product, not a mockup.