A shared technical report for your teams.

Bring development, security and platform teams together around CoreAnalyzer findings. We work with you to define volumes, Web, CLI or CI/CD access and operating conditions for your projects.

Scope my environment Compare access modes

Dedicated environments are assessed, validated and contracted for each organization.

One engine, three ways to operate it.

The analysis and report remain CoreAnalyzer. Access, capacity and operating responsibilities change according to the selected mode and active rights.

Mode Access Capacity Configuration Activation
AVAILABLE Managed SaaS AccessCoreAnalyzer Web interface. CapacityPublic Discovery, Essential or Pro plan limits. ConfigurationPlan features and targeted YAML exclusions. ActivationSelf-service according to the selected plan.
ACTIVE RIGHTS Direct CLI / CI/CD on request AccessDirect terminal access or a pipeline prepared on request. CapacityLimits associated with the active access and project scope. ConfigurationOptional CLI YAML; branch, secrets, YAML and quality gate scoped for CI/CD. ActivationCLI according to active rights; CI/CD integration prepared on request.
TECHNICAL SCOPING Dedicated environment AccessInterfaces and workflows agreed for the organization. CapacityReserved capacity or dedicated infrastructure according to contract. ConfigurationProject limits, access, security and retention validated together. ActivationTechnical scoping, measured pilot and quotation.

Enterprise addresses requirements beyond standard access and quotas. Its scope is defined by quotation.

Define the useful perimeter, not a generic package.

Scoping starts from observable project dimensions and operating constraints. Each item becomes a documented technical or contractual decision.

Describe my requirements

CAPACITY

Projects, volume and concurrency

Maximum project size, expected monthly analyses, concurrent jobs and workload classes are measured before capacity is committed.

PROJECT SCOPE

Analysis scope and delivery rules

Relevant exclusions, authorized thresholds, CI conditions and report formats are aligned with the project workflow.

ACCESS

Web, direct CLI and CI/CD on request

Users and licenses are identified; each CI/CD integration is scoped with pipeline entry points and report consumers.

SECURITY

Exposure, storage and retention

Network exposure, access controls, storage, retention and report protection are defined for the agreed operating mode.

OPERATIONS

Validation, monitoring and support

The pilot criteria, operating responsibilities, monitoring expectations and support perimeter are documented before production.

Isolation is an architecture decision, not a checkout option.

When standard SaaS capacity is not suitable, CoreDevPro can study a reserved or dedicated operating environment. Its perimeter is only confirmed after technical validation and contract.

SUBJECT TO TECHNICAL VALIDATION
  1. Repositories and pipelines
  2. Controlled access
  3. Assigned capacity
  4. CoreAnalyzer
  5. Reports and exports
  6. Retention and purge

What can be scoped

  • Reserved analysis capacity or a dedicated infrastructure, according to the validated contract.
  • Controlled network exposure and analysis workers that are not publicly exposed.
  • Storage, retention and purge rules adapted to the agreed data flow.
  • Project-size, monthly-volume and concurrency limits established from measured workloads.

From requirements to measured validation.

The engagement advances through explicit checkpoints so that capacity and security promises remain connected to the real workload.

  1. 01

    Scope

    Identify projects, technologies, volumes, access paths and security constraints.

  2. 02

    Technical proposal

    Define the access mode, capacity, responsibilities, data flow and contractual perimeter.

  3. 03

    Measured pilot

    Validate representative projects and operating conditions against agreed acceptance criteria.

  4. 04

    Production

    Activate the validated environment with the agreed monitoring, support and change conditions.

The same evidence model, whatever the access mode.

Enterprise adapts how the service is operated. The deterministic engine and report traceability are preserved.

Deterministic analysis
The main source-code analysis is performed by CoreAnalyzer and does not require an external AI service.
Source-code handling
In the current production flow, generated reports do not retain the raw content of analyzed source files.
Protected reports
Native .cdp and JSON or encrypted .cdp exports are available according to the active rights and selected workflow.
Explicit perimeter
Views, exports, quotas and operating conditions remain bounded by active rights and the accepted scope.
Read security and data processing Understand report formats Read the CLI workflow

Start with your real constraints.

Tell the CoreDevPro team about your projects, expected volume, integration environment and security requirements. We will identify the defendable CoreAnalyzer operating model.

Scope my environment