Migrating from Probely to middleBrick

Probely does not provide a native import path into middleBrick. Export your current findings as a structured file, such as JSON or CSV, from the Probely dashboard. Include finding titles, descriptions, severity, affected endpoints, and any notes you have added. If Probely offers an API, use it to pull the latest scan results so you have a repeatable data source for migration.

middleBrick does not ingest external scan files. To rebuild history, rerun scans for each API using the same URL and authentication setup. Start with the Free tier to validate coverage, then run Standard or Deep LLM scans where relevant. Record scan timestamps and scores externally, for example in a CSV, so you can correlate findings and track score drift over time. This manual baseline becomes your replacement for Probely’s historical view.

During migration, retain your existing Probely CI checks until middleBrick is proven in your pipeline. For GitHub Actions, add a parallel job that runs middlebrick scan <url> with JSON output, but do not fail the build on its result yet. Compare Probely and middleBrick outcomes for a subset of endpoints to confirm expected signal. When the two align, switch the CI gate to use the middleBrick CLI and remove the Probely step.

middlebrick scan https://api.example.com --output json

Probely may expose proprietary tests or integrations that middleBrick does not replicate. middleBrick focuses on OWASP API Top 10 coverage, OpenAPI spec validation, and LLM security probes, but it does not perform active SQL injection or command injection testing, nor does it discover business logic flaws. Compensate with targeted manual tests and, where needed, a dedicated penetration test for high-risk areas. Use the CLI output to feed custom scripts for checks you previously automated.

Migrating to middleBrick gives you a self-service, black-box scanner with a concise risk score and prioritized findings across authentication, injection surfaces, authorization, and LLM security. The platform supports OpenAPI parsing, authenticated scans with Bearer or API key, and continuous monitoring with email and webhook alerts. Next steps: inventory your APIs, run a baseline scan with the Free tier, upgrade to Starter or Pro to enable authenticated scans and monitoring, and formalize the GitHub Action gate in your CI pipeline.