Open Platform Contact EspoDev

Evaluation guide

Questions from architecture and security reviews

Answers to the questions enterprise architects and security teams ask before a design review. Each answer states what the source code and deployment records support. Where an answer depends on a commercial agreement, the page says so.

Scope

What Open Platform is for

Which applications is it designed for?

Internal web applications and services: forms, workflows, reports, dashboards, integrations and APIs used inside an organization. The application template is TypeScript on Bun, Fastify and React. Services in other languages can be integrated when they meet the application contract: a health endpoint, the platform's sign-in headers and Prometheus metrics.

Who approves a change?

The people given review rights on the application's repository. They can include the business owner of the application, not only developers. Each change can be tried in its preview environment, a working copy of the application with the change in it, before it is approved.

What happens to our spreadsheets and existing systems?

They stay in place. Applications reach other systems through HTTPS APIs, with credentials kept as encrypted secrets. Requests to public endpoints are allowed by default; reaching systems on private networks is configured for each deployment. Replacing a spreadsheet with an application is an ordinary request to the builders.

What is it not designed for?

It is not a visual application builder, a public website builder or a consumer hosting service. Applications are code in git, written by developers and an AI build agent on a shared template.

Does it replace our developer portal, CI system and AI coding tools?

It provides the system in which internal applications are requested, built, reviewed, deployed and administered. Each underlying layer, including git hosting, CI and the identity provider, can use a built-in option or an integration with the system you already run. The bill of materials lists every layer.

Operations and recovery

Availability, recovery and upgrades

Is there a high-availability configuration?

Yes. A platform can run on three servers with an embedded etcd cluster, with the git service served from all three. This configuration has been deployed end to end on DigitalOcean. On Azure, AKS provides the managed control plane.

What are the recovery points?

Application databases are backed up nightly, so the maximum data loss for an application database is one day. The platform's own database has continuous point-in-time recovery. Backups go to an S3-compatible store, with an off-site copy when a target is configured, and a weekly job restores the latest application backups and fails visibly if one does not restore. Recovery time objectives are agreed per engagement.

How are upgrades and rollbacks done?

The platform's desired state is stored in git and applied by GitOps, so an upgrade is a reviewed change to that repository and a rollback is a revert. An application deployment that fails leaves the previous version running.

Who operates and supports it?

EspoDev deploys the platform and provides support. The split of operational responsibilities between EspoDev and your platform team, and the support terms, are agreed per engagement.

Integrations

Built-in options and integration options

What is the difference?

A built-in option is selected through an existing setting, mode or deployment module. An integration option requires integration work at the integration point documented for its layer in the bill of materials.

Who builds and maintains an integration?

EspoDev implements the integrations selected for a deployment. Before the design review, we complete the bill of materials for your environment and list each integration with its integration point, so its scope is known before work starts. Maintenance of integrations across platform upgrades is part of the support agreement.

Security evidence

What your security team can review

What is available for review?

The complete source code (AGPL-3.0), the admission policies and deployment configuration in git, the architecture diagrams with each component traced to its source, and published threat models. The forge's threat model lists each protection with the test that enforces it.

Does Open Platform hold third-party certifications?

No independent certifications, such as SOC 2 or ISO 27001, are claimed. Because the platform runs on your infrastructure, it operates inside your own compliance scope, and your security team can review the source code and configuration directly.

Where does our data go?

Application data is stored in the databases and storage of your deployment. It leaves only through the flows in the data flow table: the AI build agent's calls to your model provider, query results returned to a user's own AI assistant, applications' outbound requests, alerts and build downloads.

AI governance

How AI usage is controlled

Can AI-authored changes reach production without a person?

Only if you configure it. On the platform, yes by default: a pull request created for an issue merges once it passes checks and review. Setting AUTO_MERGE_ISSUE_PRS=0 requires a person to merge. On the forge, the AI build agent cannot merge its own changes; in a repository where a person turns on autonomy, approved changes that pass checks merge in that person's name. The history records which rule applied.

How is AI spending controlled?

The platform's AI build agent has configurable per-organization spending ceilings and a circuit breaker that stops work when spending rises too fast. The forge has a weekly budget, and its agent pauses when the budget is reached.

How is untrusted content handled?

Agents running a task receive a token limited to that task: on the platform, one repository (for a planning agent, one organization) with no access to CI workflow files. In the forge's built-in assistant, content from outside users is marked as untrusted, and a write the user did not request waits for the user's confirmation. See MCP access.

Commercial model

How an engagement is structured

How is it priced?

The software is open source under AGPL-3.0. An engagement consists of a platform deployment, the selected integrations and support, provided by EspoDev, plus a forge for each developer who needs one. Pricing is quoted per engagement.

What does the AGPL-3.0 license require?

The AGPL-3.0 requires that modified versions offered to users over a network make their source available to those users. Applications you build on the platform are separate programs; review the license with your counsel for your situation.