OHIYO

AI social media management: set it up once, and AI handles topic selection, copy, images, and on-schedule posting every day.

What it is

A multi-tenant SaaS. You configure schedule entries (which platform, what time, auto-publish or wait for approval), and AI produces the post on time and publishes to X and Telegram; for Xiaohongshu and IG, it generates the content and you post it manually. Billing uses credits on a pay-as-you-go basis, and you can also bring your own AI key. Four login options: Google, email, EVM wallet, Tron wallet.

Problem it solves

The creator's pain isn't writing a single post — it's having to post every day. No single day is hard, but there is no day you can skip.

Use case

In the evening, open the approval inbox, AI has produced three drafts on schedule, you tweak a word or two and approve; the actual publishing is done by another machine in the backend, and your account credentials never pass through the website layer.

Conversational console (demo data): brainstorm topics, write copy, and configure scheduling in one sentence

Approval inbox (demo data): AI drafts, you approve before it goes out

Highlights

• Two revenue rails: Stripe credit card top-ups plus on-chain stablecoins. For crypto, instead of giving every person one address, each order gets a unique decimal tail (you pay 10.0347, and the system recognizes you by 0347); whether you overpay or underpay, it is credited according to the actual amount received.
• Key isolation: All platform credentials are encrypted at rest and only decrypted at the moment the backend worker publishes; even if the outward-facing machine is compromised, your social media accounts can't be stolen.
• Three tiers of AI action: drafting happens directly, creating a schedule defaults to waiting for approval, and actual publishing, recharging, or changing payment requires your confirmation; "approve everything" is kept where the AI cannot read it, so malicious instructions hidden in webpages cannot trick it.

Where it stands

Written in 25 days, 126 commits, 1,651 tests. A launch-readiness audit found over forty issues, six of which could lose money, and they were fixed in two days. The code is complete, not yet publicly launched, no real users. The backstory is worth mentioning: the earlier version with the same name took 94 days and 715 commits. I abandoned it and restarted on the same morning, changing the product definition from "help you create" to "keep posting for you".