Distribution
26 platforms in parallel, without the copy-paste.
MarquIQ posts to 26 platforms across social, developer communities, Q&A, publishing, and pitch surfaces, all from one brief. Idempotency keys prevent double-posts, automatic token refresh keeps connections alive, and per-platform caps protect your accounts.
The operational reality of multi-platform distribution is not the post itself. It is the idempotency, the rate limits, the token refresh, the retry logic, and the webhook observability. MarquIQ is the infrastructure that makes distribution a footnote.
What you get
26 platforms, one brief
Social, developer communities, Q&A, publishing, and pitch surfaces, all platform-native. HN and Product Hunt land in a queue for human timing; the rest ship automatically within caps.
Idempotency against double-posts
Every post has an idempotency key. Retries never double-post, even across engine restarts. This is the single most-requested feature from ex-Buffer users.
Per-platform caps
Default: two posts per platform per day, fifty global across all platforms. Configurable per organization. Caps are enforced structurally.
Token refresh with warning
Automatic OAuth refresh. Stuck tokens fire a warning at seven days. Expired tokens pause that platform without taking down the rest.
Outbound webhooks
HMAC-SHA256-signed events for every state transition: queued, published, failed, engaged. Pipe into your ops tooling or Zapier.
Full audit log
Every post event is logged with timestamp, user, and platform response. Diagnose a failure in under a minute.
How it works
- Step 1
Connect platforms once
OAuth for each platform. Scopes are minimized to what the engine needs. You can revoke any connection in one click.
- Step 2
Set caps and voice
Default caps are sensible for solo founders. Voice examples apply across all platforms; tone shifts are platform-specific.
- Step 3
Generate one brief
One research brief produces a platform-native variant for every connected surface (up to 26). Each variant is lengthed, formatted, and toned for its platform.
- Step 4
Queue with idempotency
Queue entries carry an idempotency key. Retries, platform hiccups, and engine restarts never cause double-posts.
- Step 5
Observe the loop
Webhooks fire for every state change. The dashboard shows per-platform queue depth and recent failures. Nothing silently dies.
Frequently asked questions
Which platforms does MarquIQ post to?
26 platforms across five surfaces. Social: X, LinkedIn, Reddit, Bluesky, Mastodon, Threads, Pinterest, Tumblr. Developer communities: Dev.to, Hashnode, Medium, Indie Hackers, Hacker News (queue-only), Stack Overflow blog, Lemmy. Q&A and publishing: Quora, Substack, Ghost, Beehiiv, ConvertKit. Video/content: YouTube community, TikTok captions. Pitch: Featured.com, HARO-style expert answers, Product Hunt, general newsletter paragraphs. We add platforms as they become material for SaaS signups.
How do idempotency keys work?
Every post has a client-generated idempotency key. If a post retries, the platform rejects the duplicate rather than double-posting. This is the single most important protection against double-posts from retry logic.
What happens when a token expires?
Automatic refresh using the refresh token. If the refresh fails, the engine surfaces a re-auth request in the connections page, pauses posting for that platform, and does not retry destructively.
Can I set per-platform posting caps?
Yes. Defaults are sensible (two posts per platform per day, fifty global cap across all platforms). Every cap is configurable per organization and per platform.
Are outbound webhooks supported?
Yes. HMAC-SHA256-signed webhooks fire for every post event: queued, published, failed, engaged. You can pipe events into your own ops tooling.
Distribution that never double-posts.
Connect your platforms once, set your caps, and let MarquIQ handle the operational reality. Idempotency keys, token refresh, and signed webhooks ship with the Starter plan.
Start the trial