Skip to content
Diagram. Decisions. Technical handoff.

Archful. Your AI architecture workspace.

Design the system. Record why it works this way.
Hand over the requirements, decisions, and open questions, not just the diagram.

No account needed. Create an account

Customer support AIOpen this example
Archful architecture: document ingestion, vector retrieval, orchestration, language model, and guardrails.
Recorded decision

Ground responses in source content

Retrieve relevant context at request time and preserve source metadata for citations. Evaluate retrieval quality before choosing chunk size and top-k.

A starting point for the system you have in mind

Customer support RAGKnowledge assistantAgent with toolsDocument extraction
Explore the reference library
Customer support AI / Sample project

Show how requirements
shape your design.

The support assistant must answer from approved documentation. Follow that requirement into retrieval, source citations, and the handoff.

01 / Requirements

Start with approved sources

A plausible answer is not enough. The brief calls for answers grounded in product documentation, for the support team's real workload.

02 / Decision

Record why retrieval belongs here

That requirement leads to retrieval at request time and source metadata for citations. The decision records why, not just which components to connect.

03 / Review

Leave unknowns visible

Budget, data sensitivity, and deployment constraints are still unspecified. The review identifies those gaps; it does not certify the design.

04 / Handoff

Keep the reasoning in the handoff

The exported report includes the approved-source requirement, the retrieval decision, and the unresolved constraints. The next person gets the reasoning, not just a diagram.

Your technology. Your architecture.

Design around your stack.

Bring the platforms you already use into the picture. Map how they connect, record the tradeoffs, and hand over a design your team can build.

Microsoft Azure
Product documents
Azure AI Search
Azure AI

Ground answers in your Azure stack

Map retrieval and model access, then document identity, permissions, and data residency before implementation.

Explore this design
Anthropic
Product documents
PostgreSQL + pgvector
Anthropic

Give Claude the right context

Connect Claude to your document retrieval layer. Keep source citations, context limits, and evaluation choices beside the design.

Explore this design
Google Cloud
Product documents
Vertex AI Vector Search
Vertex AI / Gemini

Plan a Gemini-powered assistant

Use custom technology fields to map a Google Cloud architecture, with retrieval, model access, and safety checks in view.

Explore this design

Architecture examples, not live integrations. No provider account is connected and no resources are deployed.

Inside Archful

Inspect the working
customer-support example.

Actual product views, from the six-component architecture to its written requirements and technical handoff.

Customer support AI: document ingestion, retrieval, model, and guardrails.Open the workspace
MDJSONSVGPNGPDF

Read the customer-support handoff

Inspect the sample brief, retrieval decision, and unresolved requirements.
Generated by Archful's own Markdown exporter.

Proposed launch pricing

One complete workflow. Room to grow.

Take an architecture from the first diagram to a documented handoff. Start on your own, manage more projects, or plan for team collaboration.

Billing cycle

Two months free with yearly Pro

Free

For individuals shaping their first architectures.

€0

Free on either billing cycle

Try the demo

What's included:

  • 2 active designs
  • Visual editor and reference patterns
  • Requirements and decisions
  • Structural design checks
  • Diagram and handoff exports

Pro

For architects managing several projects at once.

€29

Per month, billed monthly

Everything in Free, plus:

  • More active designs
  • Same complete design workflow

Exact design allowance to be confirmed.

Team

For teams designing and reviewing architectures together.

Coming soon

Pricing to be announced

Planned additions to Pro:

  • Shared team workspaces
  • Member roles and permissions
  • Collaborative architecture reviews

Team features are planned, not available today.

FAQ

Frequently asked questions

A little more about designing with Archful.

What exactly is Archful built for?

Archful is a workspace for designing AI architectures. Start with a use case, shape a diagram, document the requirements and decisions, and prepare a technical handoff.

Who gets the most out of it?

Solution architects, developers, and consultancies designing AI systems for clients or internal teams. It is particularly useful when several people need to understand the reasoning behind a design.

Can I start from an existing pattern?

Yes. The current library includes customer support RAG, a knowledge assistant, an agent with tools, and document extraction. Each is a reference to adapt, not a certified production architecture.

Does Archful generate or deploy the system?

You make the architecture decisions. Archful provides an editor, reference patterns, deterministic design checks, and exports. It does not generate or deploy infrastructure.

Can I take my work out of Archful?

Yes. Export architecture data as JSON, diagrams as SVG, PNG, or PDF, and handoff documentation as Markdown. The workspace also supports local backups.

How do I get started?

Open the workspace and choose a reference pattern or start a new design. This entry saves work in your browser, not to a cloud account. Export a local backup to keep a separate copy.

What are the Free and Pro plans?

The proposed Free plan includes two active designs and the complete core workflow: diagrams, requirements, decisions, design checks, and exports. Pro is proposed at €29 per month for more active designs, with the same core tools. Its exact design allowance is still being finalized.

When would I need Pro?

Start with Free for one or two architectures. Pro is intended for keeping more client projects or architecture alternatives active at the same time, rather than unlocking the tools needed to finish a design.

Is there a yearly billing option?

The proposed Pro options are €29 billed monthly or €290 billed yearly. Yearly works out to €24.17 per month and saves €58 compared with twelve monthly payments. Free stays €0 on either cycle. Checkout is not available yet.

Can I subscribe now?

Not yet. Checkout is unavailable and no payment is collected. You can use the local demo, which saves work in your browser. The proposed two-design Free limit is not enforced in this demo.

Bring the whole
architecture together.

From the first question to the technical handoff.