BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.

TryPost

Self-hosted social scheduling with an AI copilot running on keys you put in your own .env.

Website Source code

Category:
Marketing and SEO Tools
Maintenance:
Actively developed (last commit today)
Pricing:
Open Source
Open source:
Yes (AGPL-3.0)
Self-hostable:
Yes
Local-first:
No
Platforms:
Web, Self-hosted, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, OpenRouter, xAI Grok, Custom / OpenAI-compatible
API key storage:
User controls deployment
Key risk level:
LOW
Trust score:
82/100

TryPost schedules and publishes to a dozen social networks with an AI copilot for drafting, and exposes an MCP server so your own assistant can post through it. Self-hosted, the posts, drafts and metrics stay on your infrastructure, and the AI side runs on credentials you supply: the project's .env.example carries OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY and an XAI_API_KEY line. AGPL-3.0, with a hosted option for people who would rather not run servers.

Why this trust score (82/100)

Trust measures how the tool treats your API key and how much of that has been verified. It contains no popularity signal.

  • Key Safety 21/25: The key lives in a deployment you run yourself.
  • Request Routing 17/20: Requests go straight from you to the AI provider.
  • Transparency 20/20: Source is public under AGPL-3.0, so anyone can check how the key is handled. Key handling was located in the published source.
  • Privacy 7/15: Can be self-hosted, so the data path stays inside infrastructure you control. Analytics or error-reporting libraries are present; what they send was not established.
  • Maintenance 10/10: Actively developed, with commits within the last three months.
  • Verification Confidence 7/10: Key handling was found in the published source by BYOAIK's scanner.

What was checked

Verification tier SOURCE_VERIFIED, derived from the evidence below and not set by hand.

  • [REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
  • [STRONG · SOURCE_SCAN] The user supplies their own OpenAI key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Anthropic key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Google Gemini key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own OpenRouter key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Groq key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Mistral key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own DeepSeek key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own xAI Grok key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
  • [REPORTED · SOURCE_SCAN] References PostHog, so some analytics or error reporting is present. This scan cannot tell whether it is opt-in or what it sends. source
  • [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-09-08, about 0 month(s) ago. source

How your API key is handled

You self-host the app, so your API key lives in your own deployment. Requests are sent directly to the AI provider. Because it can be self-hosted, your key never has to touch a third-party backend.

Setup

Deploy it (Docker/compose), add your provider API key in the admin or environment config, then select models.