Public roadmap — a curated view of where SlopDrop is heading. Some items are intentionally vague because we're still figuring them out. That's honest, not evasive.

Roadmap

The plan. What we're building and when.<br>For active work, see DASHBOARD.

slopdrop.dev

Shipping Now

Target	Feature	Status
Q1 2026	CLI Core — drop, list, cat, history, rm	🚧 In Progress
Q1 2026	Authentication — Browser flow, token management	🚧 In Progress
Q1 2026	Landing Page — slopdrop.dev marketing site	🔜 Next

Next Up

Priority	Item	Status	Notes
🥇	OAuth providers	Planned	Google OAuth done. Add GitHub + Microsoft for broader team coverage
🥇	Sharing links	Planned	Expiring links, revocation. `slop link` exists but needs polish
🥇	Open-source CLI	Planned	Split Go CLI to separate repo. Homebrew tap, community contributions
🥈	Project-level permissions	Planned	Read-only access to specific projects within a tenant
🥈	Data lifecycle	Planned	Cleanup/archive stale drops, retention policies, storage reclaim
🥈	Version browsing	Planned	`?version=N` in web UI, `slop history` in CLI. Data already in D1
🥈	Audit logs	Partial	Only `secret.bypass` logged. Need full who-did-what trail
🥈	Dead link detection	Planned	Scan wiki-links and internal references, flag broken links in rendered pages
🥉	Tenant setup automation	Planned	Admin creates tenant + WAF + CF Access in one step via API

Done (shipped)

Item	When
CLI core	v0.1.0 — drop, list, cat, watch, global watch, init, tokens
Secret scanning	Every upload checked for API keys, tokens, credentials
Global watcher	`slop watch --global` — multi-project, multi-tenant, auto-retry
Admin dashboard	`admin.slopdrop.dev` — tenant CRUD, visibility toggle, usage, contacts
Docs tenant	SlopDrop docs hosted on SlopDrop (dogfooding)
Landing page + contact form	Turnstile captcha, Slack webhook notifications
Security hardening	WAF allowlist + CF Access JWT verification + rate limiting
Log rotation	Built-in daily rotation with 7-day retention
Blog platform	Any folder becomes a blog via `blog.md` — index page, Atom feed, draft support

Killer Differentiators

Features that create competitive moat.

Priority	Feature	Why It's Killer	Status
🥇	Secret Scanning	Catch API keys before they leak — trust signal	✅ Done
🥇	Zero Config CLI	`slop drop` just works — 10 second setup	✅ Done
🥈	Public Search	Searchable corpus becomes reference — network effects	⏳ Pending
🥈	Frictionless Integration	Hooks/plugins — no manual CLI calls	⏳ Pending
🥉	Enterprise SSO	SAML/OIDC unlocks enterprise deals	⏳ Pending

Rollout

Stage	Users	Gate to advance	Focus
Alpha ← current	5	Zero data loss, no auth bypasses, watcher stable for 2 weeks	Core reliability. Find the sharp edges.
Beta	20	All alpha feedback addressed, onboarding < 5 min, docs complete	Onboarding polish. Prove it works for teams, not just Sven.
GA	Open	Beta users retained 30+ days, billing live, support process exists	Growth. Marketing. Revenue.

Phase Breakdown

Phase 1: MVP (slopdrop.dev) — Current

Core product working. CLI → API → Storage. Private drops, shareable links.

Feature	Status	Spec
CLI Core	🚧 In Progress	[[specs/01-cli.md]]
Authentication	🚧 In Progress	[[specs/03-auth.md]]
API	🚧 In Progress	[[specs/02-api.md]]
Project Detection	✅ Done	[[specs/04-project-detection.md]]
Secret Scanning	✅ Done	—
Landing Page	⏳ Pending	[[specs/landing-page.md]]

Phase 2: Team Features

Multi-user, permissions, basic collaboration.

Feature	Effort	Notes
Team Workspaces	1 week	Invite members, shared drops
Permissions	3 days	Owner / Editor / Viewer roles
Audit Logs	2 days	Who did what, when
Sharing Links	3 days	Expiring links, revocation

Phase 3: Enterprise

Features that unlock enterprise sales.

Feature	Effort	Notes
SSO Integration	1 week	SAML, OIDC via CF Access
Advanced Audit	3 days	Export logs, compliance reports
Retention Policies	2 days	Auto-delete after N days
Custom Domains	3 days	drops.yourcompany.com
Storage Quotas	1 day	Per-team limits

Phase 4: Discovery & Search

Make the public corpus valuable.

Feature	Notes
Public Search	Search across public drops
Indexing	SEO for public drops
Tags & Categories	Organize drops
API for Search	Programmatic access

Stretch Goals (Unlock When...)

Like Kickstarter stretch goals. Right ideas, wrong time. Concrete triggers.

Features

Feature	Unlock When	Why Wait
Watch mode (file watcher)	50+ active users complaining about manual drops	Hard problem, multiple OSs, priority isn't clear
AI-powered search	10K+ public drops in corpus	Need data volume for ML to add value
Mobile app	Enterprise customers request it	Web/CLI covers 99% of use cases

Gates (Revenue/Growth Triggers)

Gate	Trigger	Actions to Unlock
Beta	10 active users	Open landing page waitlist, collect feedback
Launch	50 users, €100/mo ARR	Public launch, Product Hunt
Team	€500/mo ARR	Hire first contractor for support
Enterprise	5 enterprise inquiries	Build SSO, compliance features
Scale	€5K/mo ARR	Full-time focus, expand team

Global Watcher Daemon Concept

Single background process that watches all configured projects automatically.

Problem: Running slop watch manually per project is tedious. Watchers die, files don't sync.

Proposed Solution: slop daemon

slop daemon start    # Start background daemon
slop daemon stop     # Stop daemon
slop daemon status   # Show what's being watched
slop daemon add .    # Register current project with daemon
slop daemon list     # List all registered projects

Config location: ~/.slop/daemon.yaml

projects:
  - path: ~/Projects/tempo
    enabled: true
  - path: ~/Projects/docs
    enabled: true
auto_discover: false  # If true, scans for .slop files (dangerous)

Safety:

Explicit registration only (no auto-discover by default)
Lock files prevent duplicate watchers
Daemon writes to ~/.slop/daemon.log
slop daemon status shows last sync time per project
Startup on login via launchd (macOS) / systemd (Linux)

Resync capability:

On daemon start, check each project's last sync time
If files changed while daemon was down, queue them for upload
Use file mtime vs last-sync timestamp comparison

Killed Ideas

Evaluated and rejected. Not coming back.

~~Local filesystem sync~~ — Hard problem, multiple OSs, branch complexity. Use CLI explicitly.
~~Pull/download files~~ — Use slop cat for viewing. Not a file sync tool.
~~Collaborative editing~~ — Not our lane. Use Google Docs/Notion.
~~File-level branching/merging~~ — Too complex. Git exists for code.
~~Comments/annotations on drops~~ — Scope creep. Maybe Phase 4+.
~~slop.ai domain~~ — Camped at $71k. slopdrop.dev is better anyway.

See VISION for core principles and non-negotiables. See specs/architecture for technical details.

Last updated: 2026-01-29