Robrun Security · Target architecture

Clear request flow. Security-conscious design.

Explore our product vision from incoming requests to security decisions returned to your application. We are building on a tested decision API prototype with planned ready-to-use integrations, CAPTCHA and a self-service dashboard.

Decision API: tested prototypeDashboard, CAPTCHA and plugins: planned
Component diagram

Request in. Evaluation. Decision returned to your app.

The solid green path represents the API prototype; dashed connections indicate planned capabilities. This is a logical target architecture without sensitive infrastructure topology.

A request from a customer website or application flows through an integration method to the Robrun protection layer. An allow, block or planned challenge decision returns to the customer application. A planned dashboard sends policies while security reports receive events.
Product vision · Logical components and directional request/response flow. Not a deployment diagram or live-service guarantee.
Prototype

Server-to-server API

Your backend submits a security check and receives the result; enforcement remains in your application.

In development

No-custom-API options

We are exploring safe installation options such as form components, plugins and suitable proxy integration.

Roadmap

Dashboard and insights

Configure policies in a UI, activate them after integration and review security events in accessible reports.

OWASP-aligned review approach

Which problems are we working to reduce?

We use OWASP Top 10:2025, API Security Top 10:2023 and ASVS 5.0.0 to inform requirements and planned assessments. Robrun is not OWASP-certified and is not a full vulnerability scanner.

Risk areaPlanned safeguard / activityStage
Suspicious logins and brute forceLogin rate limits; later risk-based verification, related to A07 / API2.API limit prototype; login defense planned
Resource exhaustion and automationRequest limits; future bot signals and controlled blocking, related to API4 / API6.Fixed-window limits in prototype
Form spam and misuseCAPTCHA with server-side verification, replay prevention and accessible fallback.In development
Access authorizationAPI-key authentication; separate UI access rules and tests, related to A01 / API1.API-key prototype; broader review planned
Misconfiguration and security loggingSafe defaults, policy review, security-event reporting and alerts, related to A02 / A09.Planned assessments

These measures can reduce selected risks; they do not eliminate SQL injection, XSS or all OWASP risks. References: OWASP Top 10, API Security Top 10 and ASVS 5.0.

Capacity & goals

We are building toward measurable targets.

These are development targets, not verified production capacity or contractual service levels. Peak-load, failover and resilience testing are planned.

1 millionSecurity checks per month — target
50Organizations in our initial service target
99.999%Long-term availability design goal; not an SLA