Predictable pricing for legacy modernization.

Apolast charges a one-time integration fee to deploy the platform and parse your codebase, followed by a flat annual subscription to keep your system graph, tests, and specifications up to date. Get a clear cost structure before the project begins.

Request a custom quote

Two-step pricing structure.

We align pricing with typical software migration phases.

Audit & Integration

A one-time fee to deploy Apolast on your infrastructure, parse your codebase, configure local models, and generate the initial dependency graph. The cost is calculated based on codebase lines of code, module count, and system complexity.

Includes: On-premises deployment, abstract syntax tree (AST) parsing, local LLM configuration, baseline system graph, and initial characterization test suite.

Annual Subscription

An annual flat-rate license. The dependency graph updates automatically via CI/CD integrations on every commit. Engineering teams use the platform to generate pull request-ready specifications, automated tests, and Jira tasks.

Includes: Automated graph updates, specification and test generation, Jira task creation, CI/CD pipelines, and seat-based or project-based platform access.

Licensing Options

Choose a plan based on your deployment requirements, codebase size, and team structure.

Enterprise

$50,000 – $250,000+ / year

Fixed annual pricing based on codebase volume and team size. Includes on-premises deployment, unlimited specification and test generation, and dedicated technical support.

Designed for: Financial institutions, insurance companies, government agencies, critical infrastructure operators, and organizations with strict data-residency requirements.

SME & Mid-Market

$100 – $200 / developer / month

A one-time integration fee plus seat-based monthly subscriptions. Start with a single application and scale platform access as you add systems to your modernization scope.

Designed for: Engineering teams modernizing individual Java monoliths, legacy COBOL systems, or legacy ERP integrations.

System Integrators

Project-based or white-label

Pricing structures based on project scope, lines of code, or revenue-share models. Apolast automates codebase discovery and analysis to reduce manual consulting hours during migration planning.

Designed for: Consulting firms, systems integrators, and technology partners executing modernization projects for enterprise clients.

Core features.

All plans include access to the core Apolast engine. Setup scopes and deployment models are tailored to your environment.

Codebase Analysis

Abstract syntax tree (AST) parsing to map system control flow and architecture dependencies.

Continuous Updates

Dependency graphs update automatically on every commit via CI/CD pipelines.

Automated Test Generation

Characterization tests and Gherkin scenarios generated directly from system behavior.

Pull Request Specifications

Merge-ready pull requests containing technical specifications and code changes for developer review.

Task Export

Jira tasks linked to the dependency graph, containing defined technical scope and execution steps.

On-Premises Deployment

Self-hosted installation on private infrastructure, requiring no external network calls or data egress.

Optional Add-ons

Technical support SLAs

Custom integrations for proprietary build tools

Connectors for legacy infrastructure

Custom LLM fine-tuning

Flat-rate pricing model.

Apolast deploys on-premises. Because the platform runs directly on your infrastructure with no external API dependencies, we do not charge for token consumption or request volume.

Pricing is determined by the size and complexity of the codebase, the number of active engineers using the platform, and your deployment configuration.

This model provides fixed annual costs for budgeting, ensures zero data egress for security compliance, and allows unlimited usage for engineering teams.

Frequently Asked Questions

What factors influence the integration fee?

The fee is calculated based on codebase size (lines of code and module count), the legacy programming languages used, and your deployment environment requirements. We determine this fee during our initial technical review.

Are there usage limits or per-token fees?

No. Because the models run entirely on your infrastructure, there are no token charges or generation limits. Engineering teams have unrestricted access within their licensed scope.

Is on-premises deployment supported?

Yes. We support on-premises and air-gapped deployments. The platform runs entirely inside your network boundary, preventing data egress.

Can we pilot the platform on a single application?

Yes. The SME plan allows you to deploy the platform for a single legacy codebase. You can expand coverage to additional applications as needed.

Is the platform compliant with regulated industry standards?

Yes. We design for financial institutions, government agencies, insurance providers, and infrastructure operators. Deployments comply with DORA and NIS2 security frameworks.

Do you offer pricing for system integrators?

Yes. We offer project-specific, volume-based, and revenue-share pricing structures for consulting partners and system integrators.

What is included in technical support plans?

Technical support includes defined SLA response times, dedicated integration engineers, and custom connection support for legacy build tools.

How long does integration take?

Integration timelines vary by codebase size and environment. Most enterprise deployments are fully functional within 4 to 8 weeks.

Request a custom proposal.

Provide your repository details, deployment requirements, and seat count. We will deliver a custom scope and cost estimate.

Schedule a technical review