The onion-platform repository is the runnable, end‑to‑end application that integrates all libraries and services of the FLATLINEDSTAR ecosystem. It provides an HTTP API, a web dashboard, background workers, and deployment configuration (Docker, Helm, etc.).
Planning – placeholder README only.
Separating the platform (deployment, orchestration, UI) from the core libraries (onion-sdk, onion-intelligence, etc.) enables independent evolution of the service layer and easier packaging for users.
- Application – imports every other component as libraries.
- Exposes REST/GraphQL endpoints for external clients.
- Runs background workers that schedule periodic scans, monitor drift, and trigger alerts.
- Bundles the CLI (
onion-cli) for local usage and the API server for cloud deployments.
- API server (Go + Echo/Fiber) exposing scan orchestration endpoints.
- Dockerfile and Helm chart for containerised deployment.
- Simple React/Next.js dashboard (leveraging the
webUI fromOnionScan). - Configuration via YAML / environment variables (Tor address, DB path, rate limits).
# Build the platform binary
go build -o onion-platform ./cmd/platform
# Run with default config (requires a running Tor instance)
./onion-platform --config config.yamlWill be available after MVP release.
- Language: Go (primary backend) with optional TypeScript front‑end.
- Follow organization‑wide contribution guidelines.
- Unit tests for each API handler.
- End‑to‑end integration tests using Docker Compose (Tor, SQLite, API).
See the organization‑wide CONTRIBUTING.md under .github.
- Phase 1 – Scaffold the server, define OpenAPI spec, integrate SDK.
- Phase 2 – Add dashboard UI and background worker framework.
- Phase 3 – Harden security, implement rate‑limiting, CI/CD pipelines.
onion-platform is the flagship runnable product; it consumes onion-intelligence (core reasoning) and all upstream libraries. The onion-cli can also invoke platform services directly.
MIT – see LICENSE in the repository root.