Overview
PortfolioDB is a self-hosted, single-user record-keeping tool for tracking what you hold across every broker you use in one place you control. Every trade is stored as an append-only row in your own Postgres, tagged with the account it happened in. Positions, cost basis and P&L are recomputed from raw lots on every read, never persisted or rewritten, per account and merged across all of them.
FIFO and moving-average lot matching run in parallel, with per-match fee attribution. Monetary math is Decimal end to end; floats appear only at the display layer. There is no positions table. An optional read-only MCP server exposes the same engines the dashboard uses to Claude Code, Claude Desktop or Cursor over Streamable HTTP with Bearer auth, offering 47 tools, 7 resources and 7 prompts. A data-health page answers trust per symbol by checking price freshness, missing cost basis, orphaned sells and suspected splits.
An optional advisor reads a one-page document of investing rules and a live snapshot of the ledger before every brief and chat reply, and works with Anthropic, OpenAI, OpenRouter, or a fully local model through Ollama. Known limitations include single currency, no broker sync by design, no built-in login, and equities and ETFs only. Docker with Compose is the only requirement; dashboard, scheduler, MCP server and CLIs ship in one pulled Docker image under AGPL-3.0 with no telemetry.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Individuals use PortfolioDB to keep an up-to-date record of holdings across every broker in one place they control.
- Users use PortfolioDB to recompute positions, cost basis and P&L from raw lots on every read without persisting positions.
- Users use PortfolioDB to run FIFO and moving-average lot matching in parallel with per-match fee attribution.
- Users use PortfolioDB to expose portfolio engines to AI agents via an optional read-only MCP server.
- Users use PortfolioDB to check data health per symbol for price freshness, missing cost basis, orphaned sells and suspected splits.
- Users use PortfolioDB to have an optional advisor read their investing rules and live ledger snapshot before briefs and chat replies.
- Users use PortfolioDB to run the advisor with Anthropic, OpenAI, OpenRouter, or a fully local model through Ollama.
- Users use PortfolioDB to deploy dashboard, scheduler, MCP server and CLIs in one pulled Docker image.
Features
AI assistant
Natural language interface
Workflow automation
Reviews
No reviews yet. Be the first to share your experience!