Cloud Markup
GitHub Sign in Hosted beta

How it works

From architecture idea
to a considered handoff.

Follow the manual workflow shown in the actual application: design, configure, connect, validate, review, and export as supported.

  1. 01 / DESIGN

    Choose your resources.

    Start a project, search the catalog, and add supported AWS services. Arrange the canvas so the system’s structure is easy to follow.

  2. 02 / CONFIGURE

    Make settings explicit.

    Inspect properties such as Lambda runtime, timeout, and memory. Preview manual purpose changes before applying them.

  3. 03 / CONNECT

    Read the relationship.

    Review the intended permissions, delivery behavior, ordering, and retry guidance before adding a typed connection.

  4. 04 / VALIDATE

    Read the findings.

    Run supported checks and inspect the exact messages. The captured example retains a warning that AWS regional service availability is not verified.

  5. 05 / REVIEW

    Carry open questions forward.

    Revisit configuration and saved connections. Correct supported issues and document concerns that the completed checks do not resolve.

  6. 06 / EXPORT AS SUPPORTED

    Use a saved revision.

    Where your workspace permits exports, review supported CloudFormation output from a saved revision. Workload and optional application-source coverage vary; your team controls testing and deployment.

The visual evidence demonstrates design and review. It does not demonstrate a successful export or deployment.

See the feature highlights

Before you start

A few practical details.

Can I create an account?

Open the account creation page. Registration depends on current beta availability. If it is closed, contact the team about access. Existing users can sign in.

Which cloud providers are supported?

The current beta focuses on AWS. Azure support is planned, with no announced date. Check service coverage in your workspace.

Is AI-assisted creation available?

AI-assisted creation is being refined in beta. The workflow demonstrated here uses the manual canvas, catalog, configuration, connections, and validation.

Does validation prove deployment readiness?

A completed run reports the checks that ran. Review warnings and other concerns, including region availability and the requirements of your target environment.

Choose your starting point

Explore the workspace.
Read the source.

Try the hosted beta, or follow the public local setup guides. Availability differs by environment.

Try hosted beta Local setup guides Already a member? Sign in