Atheros Search
Go service and console for keyword and vector search over proxy and wireless observations.
RCLABS / PROJECTS
Projects and documentation
Atheros Search retrieves observations produced by the proxy and sensor and processed by Octopus. Schema Migrator is separate tooling for SQL change review.
Schema Migrator
Scala tooling for SQL-file validation, execution planning, catalog drift checks, and run history.
RCLabs VPN / Proxy
Rust proxy for WireGuard ingress, configured traffic handling, and audit-event publishing.
Octopus
Scala coordinator for durable ingestion, deduplication, job leases, and PostgreSQL projections.
COMPARE THE WORKFLOWS
Responsibilities
Each component has a different input and output.
Atheros Search
- Audience
- RAG builders and operators who need retrievable evidence, visible processing gaps, and source context for human review.
- Input
- Configured proxy and wireless observations
- Workflow
- Observe and ingest / Prepare and index / Retrieve and inspect
- Output
- Evidence for human review or a downstream RAG workflow
Sensor placement, configured channel coverage, observation time, and MAC randomization limit what can be seen. An observed Wi-Fi identifier does not confirm a current connection or physical device identity.
Schema Migrator
- Audience
- Platform and database engineers reviewing SQL execution order, target drift, and evidence of previous changes.
- Input
- SQL files and ordering configuration
- Workflow
- Validate / Plan / Review the record
- Output
- Run history and file changes
SQL-file snapshots preserve source files and checksums. They do not back up database data.
RCLabs VPN / Proxy
- Audience
- Network and platform teams operating WireGuard ingress, transparent proxy policies, and traffic audit pipelines.
- Input
- A configured WireGuard peer and traffic
- Workflow
- Enter / Handle / Inspect
- Output
- Records for operational review
Traffic categories are heuristics. Routing, inspection, and policy outcomes depend on deployment configuration. This synthetic sample establishes no VPN connection and sends no traffic.
Octopus
- Audience
- For platform and data teams running event pipelines that need to recover from failures and account for repeated delivery.
- Input
- Events and requests from configured streams
- Workflow
- Receive events / Coordinate jobs / Record outcomes
- Output
- A persistent record operators can inspect
Delivery can repeat. Octopus records progress and uses durable deduplication to handle replay. Records outside the configured streams are not covered.