> ## 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.

# Architect + Studio

> They aren't separate tools; they are stages in your product lifecycle. Use Architect to ignite the idea, and Studio to engineer the scale.

## The Prototyping Engine (Architect)

Architect is designed for **Speed** and **Discovery**. It handles the heavy lifting of initial setup, allowing you to go from a vague "vibe" to a working full-stack application in minutes.

<CardGroup cols={2}>
  <Card title="Why start here?">
    You don't need to know which embedding model to use or how to configure vector DB schemas. Architect makes those decisions for you so you can validate the product value first.
  </Card>

  <Card title="The Output">
    A fully deployed web URL with a custom React frontend. It's ready to show to investors, stakeholders, or early users immediately.
  </Card>
</CardGroup>

## The Scaling Engine (Studio)

Once your Architect app is validated, **Lyzr Studio** is where you go to mature the backend. Since Architect creates real Studio agents under the hood, you can seamlessly transition to Studio to fine-tune the intelligence.

<CardGroup cols={2}>
  <Card title="Why move here?">
    You need deeper control. Maybe you want to switch from GPT-4o to Claude 3.5 Sonnet for cost reasons, or you need to add a custom enterprise API tool that requires specific authentication headers.
  </Card>

  <Card title="The Output">
    Production-hardened API endpoints with rate limiting, observability, and granular governance policies applied.
  </Card>
</CardGroup>

## Real World Workflow: The Lifecycle of an App

<Steps>
  <Step title="Stage 1: Architect">
    You prompt Architect: *"Build a Resume Screener for HR."* Within 5 minutes, you have a working UI where you can upload PDFs and get scores. You send the link to your HR team. They love it but ask for better reasoning in the rejection emails.
  </Step>

  <Step title="Stage 2: Studio">
    You log into Lyzr Studio. You see the "Resume\_Screener\_Agent" that Architect created.

    You edit the **System Prompt** to include specific company values. You verify the changes in the Studio playground.
  </Step>

  <Step title="Stage 3: Production">
    The Architect app (Frontend) automatically uses the updated logic from Studio.

    The app is now "Production Ready" with refined intelligence, while retaining the beautiful custom UI Architect built.
  </Step>
</Steps>