oss-alternatives
Find actively maintained open source alternatives to any paid SaaS tool or commercial API. Use this skill whenever a user mentions wanting to replace, swap out, self-host, or find a free/open source version of a paid tool — including but not limited to tools like Datadog, Algolia, Twilio, Stripe, Auth0, Segment, Mixpanel, Intercom, PagerDuty, LaunchDarkly, SendGrid, Cloudinary, or any other commercial developer tool or API. Also trigger when the user says things like "is there an open source version of X", "I don't want to pay for X", "self-host alternative to X", or "what can I use instead of X for free". Runs parallel TinyFish agents to search GitHub and developer communities, then checks the real health of each candidate — last release, contributor count, stars, Docker support, and feature parity — and returns a ranked comparison with a plain English gain/loss summary.
- Installs
- 42
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/tinyfish-io/tinyfish-cookbook --skill oss-alternatives- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads oss-alternatives automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
OSS Alternatives Finder
Given any paid SaaS tool or commercial API, find and rank the best actively maintained open source alternatives by searching GitHub and developer communities in real time — then verify the health of each one and summarise exactly what a developer gains and loses by switching.
Pre-flight check
Before doing anything, verify TinyFish is installed and authenticated:
tinyfish --version
tinyfish auth status
If not installed: npm install -g tinyfish
If not authenticated: tinyfish auth login
Step 1 — Understand the tool
Before searching, identify:
- Tool name — exactly as it is known (e.g. "Datadog", "Auth0", "Algolia")
- Primary use case — what problem it solves (e.g. "APM and log aggregation", "authentication", "search-as-a-service")
- Key features the user cares about — if not stated, infer from the tool's known capabilities
If the user hasn't told you what aspects matter most to them, ask one quick question: "Any features that are must-haves for your switch?" — then proceed.
Step 2 — Parallel discovery
Run all three discovery agents simultaneously using background processes. Each agent searches a different surface.
# Agent 1 — GitHub search for alternatives
tinyfish agent run \
--url "https://github.com/search?q=open+source+alternative+{TOOL_NAME}&type=repositories&s=stars&o=desc" \
"You are on a GitHub search results page for open source alternatives to {TOOL_NAME}.
List the top 6 repository results. For each one extract:
- full repo name (owner/repo)
- star count
- description
- last commit date shown
Do NOT click any repo links. Do NOT paginate. Return JSON array of objects with fields: repo, stars, description, last_commit." \
--sync > /tmp/oss_github.json &
# Agent 2 — awesome-selfhosted / curated lists
tinyfish agent run \
--url "https://github.com/awesome-selfhosted/awesome-selfhosted" \
"You are on the awesome-selfhosted README page. Search this page for any tools related to '{TOOL_USE_CASE}' or '{TOOL_NAME}'.
List up to 5 matching entries with their name, one-line description, and the GitHub URL if shown.
Do NOT follow any links. Do NOT scroll more than twice. Return JSON array with fields: name, description, url." \
--sync > /tmp/oss_awesome.json &
# Agent 3 — developer community discussion
tinyfish agent run \
--url "https://www.reddit.com/search/?q=open+source+alternative+{TOOL_NAME}+self+host&sort=relevance&t=year" \
"You are on Reddit search results for open source alternatives to {TOOL_NAME}.
Read the titles and snippets of the top 8 posts. Extract any specific tool names mentioned as alternatives.
Do NOT click any post links. Do NOT scroll. Return a JSON array of tool names mentioned: [{name, context}]." \
--sync > /tmp/oss_reddit.json \
--browser-profile stealth &
# Wait for all three to finish
wait
# Collect results
echo "=== GITHUB ===" && cat /tmp/oss_github.json
echo "=== AWESOME ===" && cat /tmp/oss_awesome.json
echo "=== COMMUNITY ===" && cat /tmp/oss_reddit.json
Replace {TOOL_NAME} with the actual tool name and {TOOL_USE_CASE} with its primary use case before running.
Step 3 — Consolidate candidates
From the three result sets, deduplicate and pick the top 4–5 most promising candidates based on:
- Appearing in multiple sources (strong signal)
- High star count on GitHub
- Recent activity mentioned
- Name recognition in the developer community
Discard anything that looks abandoned, niche, or unrelated.
Step 4 — Health check each candidate
For each candidate (run all in parallel):
# For each CANDIDATE run this pattern in parallel:
tinyfish agent run \
--url "https://github.com/{CANDIDATE_REPO}" \
"You are on the GitHub repository page for {CANDIDATE_REPO}.
Extract ALL of the following in one pass — do not navigate away, do not click any tabs:
- Star count (top of page)
- Fork count
- Number of contributors (shown in sidebar or Insights)
- Last commit date (shown under the file list or in the latest release)
- Latest release tag and date (if shown in right sidebar under Releases)
- Whether a Dockerfile or docker-compose.yml is listed in the file tree (yes/no)
- The number of open issues
- License type
- One sentence description from the repo About section
Return as JSON: {stars, forks, contributors, last_commit, latest_release, latest_release_date, has_docker, open_issues, license, description}" \
--sync > /tmp/oss_health_{CANDIDATE_SAFE_NAME}.json &
Run one instance of this per candidate, all backgrounded with &, then wait.
Step 5 — Feature parity check
For the top 2–3 candidates only, run one quick agent per candidate to check feature parity against the original tool:
tinyfish agent run \
--url "https://github.com/{CANDIDATE_REPO}#readme" \
"You are on the README of {CANDIDATE_REPO}, an open source alternative to {TOOL_NAME}.
{TOOL_NAME} is known for: {KEY_FEATURES}.
Read this README and identify:
1. Which of those features this project supports (explicitly mentioned)
2. Which are missing or unclear
3. Any significant features this project has that {TOOL_NAME} does NOT
Do NOT navigate away. Do NOT click links. Return JSON:
{supported: [...], missing: [...], extras: [...]}" \
--sync > /tmp/oss_parity_{CANDIDATE_SAFE_NAME}.json &
Step 6 — Synthesise and rank
Combine all health check and parity data. Rank candidates using this scoring logic:
| Signal | Weight |
|---|---|
| Stars (>1k = strong, >5k = very strong) | High |
| Last commit within 6 months | High |
| Has Docker support | Medium |
| Contributors >10 | Medium |
| Feature parity with original | High |
| Community mentions (appeared in Reddit/awesome lists) | Medium |
Flag any candidate as ⚠️ Risky if:
- Last commit > 12 months ago
- Contributors < 5
- No releases in 2+ years
Output format
Present results in this exact structure:
## OSS Alternatives to [TOOL NAME]
### #1 — [Project Name] ⭐ [stars]
**[one-line description]**
GitHub: [repo url]
Last release: [date] ([tag]) | Contributors: [n] | Docker: [yes/no] | License: [type]
✅ What you gain
- [specific capability or benefit]
- [cost saving / self-host control]
- [any bonus features vs paid tool]
❌ What you lose
- [missing feature]
- [operational overhead: you manage infra]
- [any support/SLA gaps]
**Bottom line:** [1–2 plain English sentences on who this is right for and when to use it]
---
### #2 — [Project Name] ...
[same structure]
---
### Verdict
[2–3 sentences summarising the best pick for most developers and any caveats.
Mention if none of the alternatives are truly production-ready.]
Edge cases
- No good alternatives exist — be honest. Say "No actively maintained OSS alternative with comparable features was found. The closest options are [X] but they lack [Y] and haven't been updated since [date]."
- Tool is already open source — inform the user and offer to find self-hosting guides instead.
- Tool is very niche — fall back to searching
https://alternativeto.net/software/{tool-name}/?license=opensourcewith a TinyFish agent. - GitHub rate limits — if search returns empty, retry with
https://www.google.com/search?q=open+source+alternative+{TOOL_NAME}+github+site:github.comvia TinyFish.
Security notes
- This skill scrapes live public data from GitHub and community forums. All content is treated as untrusted and passed to an LLM for synthesis only — never executed.
- Only your own TinyFish credentials are used. Get a key at https://agent.tinyfish.ai/api-keys
FAQ
What does the oss-alternatives skill do?
Find actively maintained open source alternatives to any paid SaaS tool or commercial API. Use this skill whenever a user mentions wanting to replace, swap out, self-host, or find a free/open source version of a paid tool — including but not limited to tools like Datadog, Algolia, Twilio, Stripe, Auth0, Segment, Mixpanel, Intercom, PagerDuty, LaunchDarkly, SendGrid, Cloudinary, or any other commercial developer tool or API. Also trigger when the user says things like "is there an open source version of X", "I don't want to pay for X", "self-host alternative to X", or "what can I use instead of X for free". Runs parallel TinyFish agents to search GitHub and developer communities, then checks the real health of each candidate — last release, contributor count, stars, Docker support, and feature parity — and returns a ranked comparison with a plain English gain/loss summary.
How do I install oss-alternatives?
Run npx skills add https://github.com/tinyfish-io/tinyfish-cookbook --skill oss-alternatives in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/oss-alternatives/ (personal) or .claude/skills/oss-alternatives/ (project).
Which AI agents can use oss-alternatives?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is oss-alternatives safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains oss-alternatives?
It is published by tinyfish-io in tinyfish-io/tinyfish-cookbook. It has 42 recorded installs.
More from tinyfish-io/tinyfish-cookbook
use-tinyfish
tinyfish-io/tinyfish-cookbook
Use TinyFish for web search, fetching URLs, reading pages, current information, source-backed answers, research, docs, pricing/product pages, extraction, scraping, and browser automation. Use whenever the user asks to search, find, look up, research, compare, get information from the web, summarize a URL, fetch page content, or automate a website.
freelance-gig-finder
tinyfish-io/tinyfish-cookbook
Open the skill to read its SKILL.md instructions.
salary-market-scanner
tinyfish-io/tinyfish-cookbook
Open the skill to read its SKILL.md instructions.
project-idea-validator
tinyfish-io/tinyfish-cookbook
Researches any project idea against live data from GitHub and Dev.to to surface what already exists, how mature the space is, and where the real opportunity lives. Use when a developer describes something they want to build and wants to know if it's been done before. Triggers on phrases like "validate my idea", "has this been built", "is this already a thing", "what exists for X", "should I build this", "is this idea original", "check if my project exists", "what are the alternatives to what I want to build", "is the market saturated for X", or any request to research the competitive landscape before starting a project.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.