The Acefy journey

Where Acefy Architecture is Going

More room for architectural thinking. Less friction between an idea, its model, and the conversation around it.

We’re bringing architecture as code and visual design together, while keeping the architect in control. Here’s what you can use today and where we’re heading.

Built

A strong foundation is already here

Two complementary ways to model architecture. A shared experience for creating, refining, and presenting your ideas.

Model software and connected systems

C4 software structure and System Design 0.2 for applications, integrations, data, events, delivery, security, observability, and infrastructure.

Work in code and on canvas

Readable AAL and the visual canvas stay in sync. Start with source or shape your ideas directly on the diagram.

Compose diagrams with control

Automatic layout, styling, presentation, meaningful relationships, and manual connector routes.

Keep ownership of your projects

Local or private cloud saves, SVG and PNG exports, and portable project files keep your work in your hands.

Connected systems, made visibleSystem Design 0.2 · Available today
Uses · connectPlace order · request_responseUpdate customer · writeTake payment · request_responseCustomercustomerCustomer portalapplicationOrders APIapplicationCustomer CRMexternal systemPaymentsexternal system

Scroll across to explore the diagram.

Connect a customer portal, orders, CRM, and payments around one customer journey.

Now

Making architecture creation feel effortless

Our current focus is the experience of using Acefy: small, thoughtful improvements to the work you do every day.

Clearer composition

Make complex diagrams easier to arrange, read, and discuss.

Smoother routing and editing

Refine everyday interactions so working through a design feels natural.

Easier learning

Improve examples and guidance so the next useful step is easier to find.

Next

From diagramming toward architecture intelligence

The direction is to help architects reason about structure, relationships, technologies, and design intent—and carry that understanding forward as systems evolve.

This direction is not a feature commitment or delivery schedule.

Exploring

Making architecture knowledge easier to evolve

We are exploring deeper architecture intelligence, richer modelling, and project workflows that preserve useful knowledge over time. These are areas of interest, not promised functionality.

Independently built. Thoughtfully grown.

Help us keep building

Support helps fund the time and resources behind Acefy Architecture, while keeping core capabilities available without a contribution wall.