いま使っているツールから出発します。各カードには、実際に置き換えられる open プロジェクト、ライセンス、セルフホストの可否をまとめています。
ノート・ドキュメント・チーム wiki をひとつに
乗り換える理由: You want your team's knowledge base in a database you control, exportable and self-hostable.
Closest Notion-style block editor, local-first, AI optional.
Docs and an infinite whiteboard in the same canvas.
Fast team wiki with strong search and SSO.
表計算とデータベースのハイブリッド
乗り換える理由: Row limits and per-seat pricing bite as soon as the base becomes useful.
Turns any Postgres or MySQL database into a smart spreadsheet.
Postgres-backed, handles large tables without slowing down.
Plugin architecture, straightforward self-hosting.
チャンネルとスレッドのチームチャット
乗り換える理由: Message history limits and data residency rules push teams to self-host.
The enterprise-grade drop-in; strong compliance story.
Topic-threaded model that actually scales to async teams.
Chat plus omnichannel customer messaging.
トレース・メトリクス・ログを一つに
乗り換える理由: Per-host and per-GB billing turns observability into one of the largest infra line items.
OpenTelemetry-native APM; one tool for all three signals.
Very low storage cost at high ingest volume.
Instrument once with the vendor-neutral standard, then choose a backend.
シークレット管理と動的クレデンシャル
乗り換える理由: The BUSL relicensing left teams looking for a genuinely open successor.
Linux Foundation fork of Vault; API-compatible migration path.
Developer-first secrets with good CI and Kubernetes hooks.
クラウド横断の IaC
乗り換える理由: Same BUSL story: the workflow is a standard, the license no longer is.
Linux Foundation fork; drop-in for existing HCL and state.
Same job in real programming languages instead of HCL.
ウェブ・プロダクト分析
乗り換える理由: Cookie banners, GDPR exposure, and sampled data are all avoidable.
Cookie-free, tiny script, one readable dashboard.
Lightest self-hosted option; runs next to your app.
Web plus product analytics with funnels and retention.
ノーコードでアプリを連携・自動化
乗り換える理由: Per-task pricing punishes exactly the workflows that succeed.
Node-based, AI-agent friendly, unlimited runs when self-hosted.
MIT-licensed with a friendly no-code builder.
Scripts first: turn Python or TypeScript into workflows and UIs.
ブラウザで共同 UI デザイン
乗り換える理由: Design files are core IP; some teams need them on their own servers.
The mature open design tool; standards-based SVG and CSS.
API のテストとドキュメント化
乗り換える理由: Forced cloud sync of API collections is a hard no for many teams.
Collections are plain files in your git repo. No cloud.
Fast browser-based client; self-host the whole thing.
ホスト型バックエンド一式
乗り換える理由: Lock-in plus unpredictable scaling costs; Postgres is a safer floor.
Postgres with auth, realtime, storage, and edge functions.
Batteries-included backend with solid SDK coverage.
One Go binary with SQLite; perfect for small products.
ホスト型 ID 基盤
乗り換える理由: MAU-based pricing scales with your success, not your usage of the feature.
The enterprise default; every protocol you will ever need.
Modern multi-tenant IAM with a much lighter footprint.
Pairs with any of these for Zanzibar-style fine-grained authorization.
フィーチャーフラグと段階的リリース
乗り換える理由: Flag logic ends up wired through your whole codebase — keep it portable.
CNCF standard API — swap providers without touching app code.
Full flag platform you can run yourself.
Mature rollout strategies and a strong SDK lineup.
ショート動画のタイムライン編集
乗り換える理由: Watermarks, account requirements, and uploads of footage you may not want to upload.
The direct open counterpart; browser or desktop, no watermark.
Local-first and conversational, with agent skills and MCP.
The long-standing desktop NLE when you need real depth.
LLM のチャット UI
乗り換える理由: You want the same interface over your own models, keys, and documents.
Self-hosted UI for local and cloud models, with RAG and tools.
Multi-provider chat with agents, presets, and team accounts.
ファイル同期と共有
乗り換える理由: Storage is cheap; paying per seat to keep your own files is not.
Files plus calendar, contacts, and office — a full suite.
Focused purely on fast, reliable sync at scale.
CRM と営業パイプライン
乗り換える理由: Per-seat pricing plus paid add-ons for things most teams consider baseline.
Modern CRM built like a product, not a config surface.
Mature and customisable; runs fine on a small VPS.
CRM as one module of a full open business suite.
BI ダッシュボードとセルフサービス分析
乗り換える理由: Licences scale with viewers, so sharing insight across the company gets taxed.
The fastest path from a database to a dashboard non-engineers use.
Deeper charting and a SQL Lab for analysts who live in SQL.
Built on dbt metrics, so definitions stay in version control.
パスワード管理とチーム共有 vault
乗り換える理由: Your credential store is the one place you most want to be able to audit and host yourself.
Open-source clients and server; the direct like-for-like swap.
Lightweight Rust server that speaks the Bitwarden protocol.
Team-first sharing model with per-secret permissions.
カスタマーサポートの受信箱とチケット
乗り換える理由: Per-agent pricing punishes a growing support team, and the conversation history is the asset.
Omnichannel inbox — web chat, email, and social in one place.
Lightweight shared mailbox; runs on ordinary PHP hosting.
ニュースレターと購読者管理
乗り換える理由: Billed by list size whether or not you send, and your list is meant to be portable.
One Go binary, millions of subscribers, bring your own SMTP.
Full marketing automation once campaigns get conditional.
ソフトウェアチームの課題管理と計画
乗り換える理由: Heavy, expensive per seat, and hard to leave once the workflow lives inside it.
Modern issues, cycles, and modules without the ceremony.
Classic project management with Gantt charts, budgets, and roadmaps.
Agile-first with clean scrum and kanban boards.