Frequently asked questions

Visit the homepage for pricing and product overview, or book a discovery call.

Forge Platform provides a pre-engineered operational foundation for secure, scalable distributed systems on AWS, dramatically reducing the time, cost, and risk of reaching production-grade operational maturity.

It encodes years of platform engineering decisions into a deployable operating model built on AWS and Quarkus.

Forge is not a framework. It is a pre-engineered operating model for building production systems.

Forge is designed for teams building products expected to become operationally serious systems — not throwaway MVPs.

Typical adopters include:

  • startups preparing to move from prototype to production,
  • founding teams hiring their first senior engineers or CTO,
  • enterprise innovation teams building new greenfield systems,
  • and organizations that need enterprise-grade operational foundations without building an internal platform team first.

Forge is a strong fit when security, scalability, auditability, operational maturity, or multi-service architecture are expected requirements within the next 12–24 months.

Yes. Forge is forked into your GitHub organization and deployed into your AWS account—not into infrastructure we host.

Your engineering team retains ownership of:

  • source code,
  • cloud infrastructure,
  • deployment pipelines,
  • operational data,
  • and runtime environments.

Forge is not hosted SaaS—your services run in your AWS account, not on servers we operate.

Forge is best thought of as a production-ready platform foundation.

It combines:

  • infrastructure automation,
  • shared platform services,
  • operational tooling,
  • deployment workflows,
  • and architectural conventions

into a cohesive starting point for building production systems.

Unlike simple starter templates, Forge includes operational and organizational patterns typically developed internally over years of scaling.

Most teams eventually build versions of these systems internally:

  • authentication,
  • audit infrastructure,
  • deployment automation,
  • observability,
  • service-to-service security,
  • operational tooling,
  • and shared platform conventions.

The challenge is timing.

Early-stage teams are usually forced to choose between:

  • shipping product quickly with weak operational foundations,
  • or spending months building internal infrastructure before product velocity exists.

Forge attempts to remove that tradeoff.

Forge is designed for horizontally scalable distributed systems rather than fixed single-server capacity limits.

The platform has been validated under sustained load on production-style AWS infrastructure using:

  • ECS,
  • GraalVM native services,
  • managed AWS networking,
  • and horizontal task scaling.

Performance characteristics focus on:

  • predictable throughput under concurrency,
  • clean recovery under load,
  • stateless horizontal scaling,
  • and operational stability during traffic increases.

Actual supported user volume depends heavily on:

  • request patterns,
  • workload complexity,
  • background processing,
  • data access characteristics,
  • and deployed infrastructure sizing.

Forge is intended to support systems ranging from early-stage products through to large-scale production deployments by scaling infrastructure horizontally as demand increases.

Detailed benchmark methodology and performance data are published in the performance documentation.

Forge currently targets AWS as its primary cloud platform.

The architecture and deployment tooling are intentionally opinionated around AWS-managed services in order to reduce operational complexity and accelerate delivery.

Kubernetes is not currently a deployment requirement.

Forge instead prioritizes operational simplicity, predictable deployments, and lower infrastructure overhead for early-stage teams.

Forge integrates with core AWS services used in production systems, including:

  • VPC,
  • IAM,
  • Cognito,
  • ECS,
  • ALB,
  • RDS,
  • S3,
  • and CloudWatch.

Service selection prioritizes operational maturity, scalability, and minimizing infrastructure management overhead.

A typical production-oriented Forge deployment starts at approximately USD $130/month in AWS infrastructure costs before significant production traffic.

Costs scale primarily with:

  • user traffic,
  • data storage,
  • compute requirements,
  • and workload complexity.

Forge is intentionally designed to provide enterprise-grade operational foundations without requiring enterprise-scale infrastructure spend on day one.

Yes.

Forge is designed to be extensible rather than restrictive. Teams can:

  • add new domain services,
  • replace infrastructure components,
  • customize deployment workflows,
  • and evolve architectural patterns over time.

Forge provides a production-ready starting point, not a closed ecosystem.

Forge is commercially licensed software deployed onto infrastructure you control.

Your team owns and operates:

  • your AWS account,
  • deployment environments,
  • application code,
  • operational data,
  • and service extensions built on top of Forge.

Forge itself includes proprietary platform components and licensed runtime foundations that remain part of the commercial platform subscription.

This model allows teams to retain operational ownership and deployment control while avoiding the cost and time required to internally develop equivalent platform infrastructure.

Longer-term licensing options may become available as Forge matures.

Full technical documentation is available at https://docs.forgeplatform.software.

The documentation includes:

  • architecture guidance,
  • deployment workflows,
  • infrastructure operations,
  • observability,
  • service development patterns,
  • and production engineering practices.