Ship in code. Post without leaving it.

Indie developers use Oxhype to run build-in-public distribution from the tools they already live in. Our social media tool for indie developers ships with a CLI, a REST API, and a native MCP server — so you announce releases from the terminal, a script, or your editor without ever opening a marketing dashboard.

Get StartedWatch Demo

You'll write the code all day. Opening a social dashboard is where the streak dies.

  • Marketing breaks your flow

    Leaving the terminal to log into four apps and hand-write posts is the exact context switch that makes 'build in public' quietly become just 'build'.

  • GUI tools fight your workflow

    Click-through schedulers assume you want a dashboard. You want a command, a config, or an API call that fits into scripts and CI like everything else you own.

  • Great releases, zero reach

    You ship features and fixes constantly, but if none of it gets announced, the audience that funds indie work never hears the story or finds the product.

Oxhype treats distribution as code — driven from the CLI, the API, and your editor's AI.

Distribution that lives in your dev loop

Announce from the terminal, a git hook, or CI — the same places you already ship from.

Marketing as a separate job

Hours (that never happen)
  1. Finish the feature
  2. Context-switch to a browser
  3. Log into each social app
  4. Hand-write and post per platform
  5. Never actually do it

With Oxhype

Seconds, in-flow
  1. Run one CLI command or API call
  2. AI drafts native posts per platform
  3. Review in the terminal or your editor
  4. Publishes across every channel

Wire a release announcement into your deploy script once and every future ship posts itself.

A social API that thinks like a dev tool.

The developer-first surfaces that let you run build-in-public distribution without leaving your workflow.

Post From the Terminal

Announce a release without touching a browser. The Oxhype CLI drafts and publishes across every connected platform from a single command, so sharing a ship is as fast as running your tests.

  • One command to publish

    Draft, schedule, and post to every platform straight from your shell — no dashboard round-trip.

  • Scriptable by design

    The CLI slots into Makefiles, release scripts, and dotfiles like any other dev tool you own.

A terminal running an Oxhype CLI command that drafts and publishes a release post across platforms

Announce Straight From CI/CD

Wire our REST API and webhooks into your pipeline so a merged release or a tagged version fires a coordinated multi-platform post automatically — the build-in-public update ships with the build itself.

  • Release-triggered posts

    Fire announcements on a tag, a deploy, or a GitHub release with a single API call in CI.

  • Programmatic scheduling

    Queue changelog and milestone posts from your own scripts, versioned alongside your code.

A git tag triggering a CI job that calls the Oxhype API to announce a release across social platforms

Publish From Your AI Editor

Oxhype ships a native Model Context Protocol server. Point Claude Desktop, Cursor, or any MCP client at it and manage your whole queue conversationally — draft, schedule, and review posts without leaving your editor.

  • Editor-native queue control

    Ask your AI agent to announce the release you just merged, right where you wrote it.

  • One-line MCP setup

    Add the server to your MCP config once and drive Oxhype from any compatible client.

Cursor using the Oxhype MCP server to draft and queue a build-in-public post from inside the editor

How indie hackers actually stay consistent

  • Relying on willpower to open a dashboard

    If posting means breaking flow to use a GUI, it won't happen consistently. Driving it from the terminal and CI removes the context switch entirely.

  • Click-through schedulers

    GUI-only tools don't fit a workflow built on scripts and automation. A CLI and API make distribution just another part of your pipeline.

  • Skipping marketing altogether

    Shipping in silence means the audience that sustains indie products never forms. Automated announcements build it as a side effect of shipping.

Driven from the tools you already use

Publish natively to every major platform, driven by a CLI, a REST API, webhooks, and a native MCP server.

  • CLI
  • REST API
  • Webhooks
  • MCP
  • LinkedIn
  • Bluesky
  • YouTube
  • TikTok

Build in public without breaking flow.

Run your entire distribution from the terminal, your scripts, and your editor — never a separate marketing app.

Marketing as an interruption

  • Context switch kills it

    Leaving code to open four browser apps is the friction that ends most build-in-public habits.

  • GUI tools don't fit

    Click-through dashboards can't be scripted, versioned, or wired into the pipeline you already run.

  • Releases ship in silence

    Constant features and fixes go unannounced, so no audience forms around the work.

  • Manual posting per platform

    Rewriting and reposting the same update for each network is tedious enough to skip entirely.

With Oxhype

  • Post without leaving code

    A CLI command, an API call, or an editor prompt publishes everywhere — no browser, no flow break.

  • Distribution as code

    The CLI and API drop into scripts, Makefiles, and CI so posting is versioned like everything else.

  • Every ship gets announced

    Wire announcements into your deploy once and future releases post themselves automatically.

  • One input, every platform

    Oxhype can draft native captions per feed with optional AI, so one update lands everywhere.

Related

Frequently Asked Questions

Can I post without opening a dashboard?

Yes. The Oxhype CLI drafts and publishes across every connected platform from a single terminal command, and the REST API and MCP server let you drive everything from scripts or your editor — no browser required.

Can I announce releases automatically from CI/CD?

Yes. Wire our REST API and webhooks into your pipeline so a git tag, a deploy, or a GitHub release fires a coordinated multi-platform announcement automatically. The build-in-public post ships with the build.

Does it work with Claude Desktop or Cursor?

Yes. Oxhype ships a native Model Context Protocol server. Add it to your MCP config once and manage your queue conversationally from Claude Desktop, Cursor, or any MCP-compatible client, without leaving your editor.

Do I still have to write a post for every platform?

No. You provide one update (from the CLI, the API or your editor) and Oxhype publishes it to each platform, with an AI-drafted caption per platform if you turn it on, so a single command lands the right post everywhere.

Which platforms can I publish to?

Oxhype publishes natively to LinkedIn, Bluesky, YouTube, TikTok, and Instagram. Bluesky and other direct integrations pair naturally with a developer, build-in-public audience, all driven from your own tooling.

Join to automate your social media posting

50+ early adopters are already automating their content & cross-posting pipelines.

Benefit from early adopter perks