THE INDEPENDENT CONTROL LAYER
Different teams. Different coding tools. One organisation’s standards.
ARKO brings your context into the work, independently checks changes and returns the evidence.
Explore the interactive workspace
Organisation context ↔ Review evidenceBring organisation context into the code review. Return findings and proposed changes to the developer.
01 / ORGANISATION CONTROL
Set the context centrally. Bring it into connected workflows. Follow the findings, changes and completed checks back to your team.
CHOOSE A STANDARD
Use the organisation’s approved data service.
Organisation policy → Connected workFOLLOW THE WORK
Policies inform the work. Evidence returns for review.
REVIEW EVIDENCE
Example policies and results. Available controls and gate behaviour depend on your integration and organisation configuration.
EXPLORE THE PRODUCT
Inspect the code, run the example scan, apply changes and verify them. Follow the same work from the IDE to the agent and into the Control Plane.
Open the dedicated demo ↗arkoINTERACTIVE WORKSPACEAdd an AI assistant that can look up a customer’s orders. Follow our approved services, protect credentials and keep the request bounded.
The coding agent proposes the change. ARKO supplies the independent check. Follow the same findings across both views.
The local change, policy and recheck belong to the same record. This view updates as you use the demo.
Interactive demonstration with synthetic code and results. No live scan or application test runs here.
THE MOMENT THAT MATTERS
A finding is easier to act on while the developer or agent still has the task in context. Explore where the feedback enters the workflow.
Check the change, review the fix and recheck inside the task. Configured gates determine what happens next.
THE ORGANISATION BEHIND THE CODE
A line of code is only part of the picture. Connect it to the application, approved patterns and the standards your organisation needs to uphold.
arkoShared contextPolicies ⇄ EvidenceBring the route, authentication boundary and data flow into the finding. Judge it against the application’s actual responsibilities.
Your team’s decisions and updated policies inform subsequent checks across connected work.
FROM THE FIRST EDIT TO THE RELEASE DECISION
Different stages expose different risks. Follow the workflow to see where checks, gates and evidence fit—and what each integration needs.
CONTEXT & POLICY
Bring application context, approved patterns and organisational policies into the review. Make the intended architecture visible before judging the change.
Supply and maintain the context relevant to the application and team.
Explore system contextDEVELOPER WORKFLOW
Find risks, inspect the explanation and review a proposed fix without leaving the supported editor. Recheck the updated source with the scope kept clear.
Available background checks follow the extension settings and organisation configuration.
Install the extensionMCP WORKFLOW
Connect ARKO to your coding agent through MCP. The agent can submit source and dependencies, explain findings and check the changes it makes.
MCP supplies tools. An agent’s completion behaviour also depends on its instructions and configured hooks.
Connect MCPREPOSITORY GATES
Use repository checks and configured hooks to make the policy part of the development workflow. Choose how a failed or incomplete check should affect the next action.
Review the generated gate configuration; different clients have different enforcement points.
Explore repository gatesPULL REQUESTS
Connect repository and CI checks to the change under review. Keep findings, proposed remediation and the checked scope visible to the people approving the merge.
A failed check blocks merging only when the repository’s required-check policy enforces it.
Explore delivery checksDEPENDENCIES & ARTEFACTS
Inspect dependency and supply-chain risk, review software inventory and carry evidence about the checked source or artefact into the release decision.
Source, dependency and artefact checks cover different things. Confirm the available integrations for your pipeline.
Explore evidence scopePRODUCT DIRECTION
Simulation exercises a running application in an isolated environment, looking at routes, boundaries and behaviour. Its value is evidence from execution alongside findings inferred from source.
Future-direction overview. Confirm current availability and requirements with ARKO before planning this part of your rollout.
Explore the simulation workflowPRODUCT DIRECTION
Evidence from a deployed system answers different questions from a source scan. Bring the intended observation scope, data boundaries and review responsibilities into the rollout discussion.
Future-direction overview. Confirm current availability and requirements with ARKO before planning this part of your rollout.
Discuss your environmentWorkflow overview. Controls and availability depend on the integration, deployment and agreed scope.
HUMANS. AGENTS. THE SAME STANDARD.
Inspect the finding, its context and the proposed change. Stay in control of what is applied.
Set up the IDE ↗Give your agent ARKO tools through MCP. Bring the independent result back into its next action.
Connect your agent ↗Use supported hooks and repository checks to apply your policy. Enforcement depends on the integration and configuration.
Explore gate setup ↗INSIDE THE CHECK
Deterministic checks, relevant context and configured model perspectives contribute to the assessment. ARKO Core evaluates the findings and proposed changes.
Use deterministic checks for recognised risks. Keep the finding and its supporting source visible before adding further analysis.
FROM INFERENCE TO EXECUTION EVIDENCE
Walk through an example customer-isolation check: from a source finding to a reproduced behaviour, then a recheck of the changed application.
A source finding suggests that an authenticated customer may be able to request another customer’s order. It has not been reproduced yet.
Interactive illustration of the product direction. No application or security test runs here. Confirm current simulation availability, prerequisites and scope with ARKO.
Discuss simulation for your environment ↗GOVERNANCE ACROSS YOUR ORGANISATION
Teams use different editors, agents and repositories. ARKO connects their work to centrally managed policies, then brings the findings, fixes and review context back.
arkoBring your organisation’s approved package choices into connected coding workflows.
POLICIES OUT
A common baseline reaches each connected workflow through ARKO.
Select a team to follow its connection. Select it again to return to the whole organisation.
Illustrative organisation and policies. Available controls depend on your integration and organisation configuration.
THE DECISION LEDGER
Follow the finding, the change, the reviewer’s decision and the result of the next check. Give the next person a record they can inspect.
Keep human, agent and pipeline activity distinguishable. Follow decisions to fix or accept a finding, with the relevant context and responsibility visible.
A check of edited files, a full repository review and a running-system observation establish different things. Preserve that distinction in the evidence.
Discuss your evidence requirementsWhat the check found in the code submitted from that session.
Other files and subsequent changes need their own coverage.
The findings and completion status for the reviewed change and configured check.
Required-check policy determines whether that result blocks a merge.
A broader view of repository findings, dependencies and recurring exposure.
Coverage is tied to the revision, included files and completed checks.
What the relevant artefact and dependency checks establish about that build.
An artefact result does not by itself demonstrate a running exploit or operational behaviour.
The proposed workflow would record what was reproduced or observed within an agreed running environment.
Executable simulation and runtime availability need confirmation before rollout.
DEPLOYMENT & DATA BOUNDARIES
Start with where your code, inference and evidence may run. Review the supported configuration with ARKO before committing to a rollout.
Illustrative architecture boundary. Select a mode to compare; the supported configuration is agreed with ARKO.
Connect supported tools and repositories to ARKO’s managed service. Agree organisation access, policies and the evidence your stakeholders need.
Discuss this deploymentDiscuss the right workspace and integration setup.
If your organisation requires an approved model provider or customer-owned inference, start with those constraints. Confirm the supported provider, account boundary and operating responsibility before rollout.
Discuss this deploymentEnterprise architecture discussion; not a self-service availability claim.
Discuss which workloads need to run within your infrastructure, the connectivity they require and how findings return to the Control Plane.
Discuss this deploymentConfirm supported runner and deployment options with ARKO.
For restricted or isolated environments, define network, identity, inference and evidence requirements together. Establish what is supported and what requires additional work.
Discuss this deploymentRequirements-led discussion; air-gapped availability is not assumed.
Findings and minimal snippets retained. Your full source is not retained after scanning, and your code is not used to train models. Read the processing details ↗
WHAT CHANGES
See the finding, proposed change and recheck in the developer and agent workflow.
Follow organisation policy out to connected workflows and the evidence back.
Keep scope, completed checks and decisions attached to the outcome.
YOUR NEXT STEP
Add the free extension or connect your agent. Follow a first check from code to result.
Choose your setupExplore organisation policies, repository oversight and evidence with the ARKO team.
Talk to ARKO