> ## Documentation Index
> Fetch the complete documentation index at: https://docs.architect.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Architect?

> The software landscape has shifted. Building apps is no longer about writing boilerplate; it is about orchestrating intelligence.

The software landscape has shifted. Building an app is no longer about writing boilerplate — it's about orchestrating intelligence. Architect exists because the modern "AI app" stack is powerful but painfully fragmented, and most of the teams who need these tools the most can't afford to assemble that stack themselves.

## The Fragmentation Problem

Before Architect, building an "Agentic App" (say, an automated legal reviewer) meant stitching together a disjointed, complex stack — and maintaining every piece of it:

* **LangChain / LlamaIndex** for agent logic and orchestration
* **Pinecone / Weaviate** for vector memory and retrieval
* **FastAPI** to expose your agents as endpoints
* **React / Next.js** for the user interface
* **Auth, a database, hosting, and CI/CD** to actually ship it

Each layer needs its own setup, glue code, and ongoing upkeep — and a single engineer has to understand all of them.

<Info>
  **Outcome: 6+ weeks.** Typical time to a working MVP for a single internal tool — gated on scarce engineering time and a high upfront cost before you've even validated the idea.
</Info>

## The Architect Advantage

Architect unifies that entire stack behind a single prompt. The agent logic, the vector memory, the API layer, the UI, the auth, the database, and the hosting are all handled for you — so Product Managers, Founders, and non-engineering teams can self-serve complex software needs without waiting on an engineering queue.

<CardGroup cols={2}>
  <Card title="Speed as a Feature" icon="clock">
    In the enterprise, the backlog is the enemy — internal tools often sit there for months. Architect cuts build time from weeks to minutes, letting you bypass the backlog entirely and validate ideas the same day you have them.
  </Card>

  <Card title="Deterministic Reliability" icon="arrow-trend-up">
    AI code generators love to hallucinate packages and ship broken builds. Architect runs a multi-agent validation loop instead: it writes the code, runs it, reads the errors, fixes them, and only then shows you a working app.
  </Card>

  <Card title="Built for Non-Engineers" icon="user-group">
    No environments, API keys, or framework decisions to make. If you can describe the outcome you want, you can build and ship the app that delivers it.
  </Card>

  <Card title="Real Code You Own" icon="code-branch">
    Architect isn't a black box. Every app is real React/Next.js + Lyzr backend code you can push to your own GitHub, export, and self-host.
  </Card>
</CardGroup>

### Comparison: Traditional Dev vs. Lyzr Architect

| Feature               | Traditional AI Dev        | Lyzr Architect                  |
| :-------------------- | :------------------------ | :------------------------------ |
| **Setup Time**        | Days (Env, Git, API keys) | **Instant (Zero setup)**        |
| **Agent Integration** | Manual (LangChain code)   | **Automated (Lyzr Agentic OS)** |
| **Frontend**          | Manual (React/Vue)        | **Auto-Generated (Shadcn UI)**  |
| **Cost to Build**     | \$10k+ (Eng hours)        | **\~\$10 (Compute credits)**    |