Home / Articles

How Chromoly Builds Apps: Blueprint, Review and Runtime

Chromoly separates the description of an app from the shared machinery that renders and runs its supported features. The saved blueprint gives planning, compilation and change review a common structure.

The underlying principle

AI interprets the requested system and proposes a blueprint or edits. The blueprint describes pages, records, APIs and workflows. Shared runtime components implement supported behaviour. A structured definition can include executable logic; it should not be presented as proof that no generated code or runtime error is possible. Product definition.

From request to working preview

How edits are reviewed

The change review compares the saved version with the generated candidate. It shows additions, modifications, removals and dependent features. The dependency map connects blueprint elements such as fields, APIs, components, pages, workflows and roles. Review and dependency map documentation.

Why use a shared structure?

A common representation helps locate related parts of the app and apply consistent components. It also defines a support boundary: a requested feature must be expressible and supported by the platform. A visual match to a demo is not evidence that an unsupported integration or workflow will run.

What to compare with other approaches

Evaluate the visibility of changes, the supported app patterns and the operating model. Code-oriented tools may offer different extension and collaboration options. Chromoly’s approach is a product choice, not proof that dependency analysis or safe release processes are unavailable elsewhere.

Where the platform data services run

Chromoly plans to migrate the primary platform database, authentication, file storage and realtime services to self-hosted Supabase on UpCloud in Stockholm, Sweden. The migration is not yet complete. Current services continue to use Supabase Cloud, Vercel and Hetzner as applicable until migration and verification are complete. In the planned setup, Chromoly will operate the Supabase software and manage its configuration, access controls, updates and recovery arrangements. UpCloud will supply the underlying infrastructure. This is self-hosted Supabase software, rather than the Supabase Cloud managed service. AI providers and connected services have separate processing arrangements. See hosting and data access and the subprocessor list for current services and migration scope.

Operational limits still matter

Static analysis cannot see every dynamic relationship or external effect. Saved-version restoration does not reverse data edits, messages or payments. Connected services need their own credentials and tests. Managed implementation and maintenance are available now, with scope and pricing agreed for your project. Workflow operations; plans and service scope.

Frequently asked questions

What does the compiler build from?

The saved AppSpec blueprint describes supported app structure and behaviour. The compiler and shared runtime use that definition to assemble the app.

Does the architecture guarantee a production-ready app?

No. Generated output requires review, representative behaviour tests, permission checks and configuration of connected services before use.

Related reading

Chromoly is open for business. Managed service and Partner access are available now with custom pricing. Book a call to discuss your project, or read the product guide.

Discuss your system with us.

Bring your workflow and requirements. We can scope a Managed build and ongoing service around them.

Book a discovery call