Back to app

Getting Started

What Amira is, how the Spec → Build → Deploy → Companion pipeline works, and how to start your first project.

Parts of this page are out of date

The four-stage pipeline below, the e-signature gate between specification and development, the Deploy Agent and the companion agent describe a flow that is not in the product. Approvals are recorded, not required: nothing blocks a session, and there is no lock. Deployment and companion agents are not built.

For how specification actually works today, see Working with Specifications. This page needs a rewrite with new screenshots.

Amira turns a plain-language description of the app you need into a governed, deployed application — backed by your data lake and your policies. You describe the outcome; the platform's agents specify, build, deploy, and maintain it, with a human approval gate at every irreversible step.

The pipeline#

Every application moves through four stages, in order. A human approves each irreversible step — nothing is built from an unapproved spec, and nothing is deployed without sign-off.

1 · Specifications

The Spec Agent interviews you and produces a builder-ready specification: functional and non-functional requirements, acceptance criteria, a capability graph, and any open gaps or decisions. You iterate in plain language until the spec is complete.

2 · Development

Once a spec is approved, the Build Agent writes the application in a sandbox, wiring in the skills and data sources the spec references. Progress is scored against the spec's acceptance criteria on a live compliance matrix.

3 · Deployment

With approval, the Deploy Agent promotes the built application to a running URL.

4 · Companion

Every deployed application gets a companion agent, so other apps and people can call it as a reusable capability.

Start your first project#

1
Create a project

From the home screen, choose New Project.

2
Describe what you want — or import it

Type a sentence or two describing the app you need. Or import an existing codebase and let Amira reverse-engineer a starting spec from it.

3
Iterate with the Spec Agent

The agent asks what it needs, writes the specification into your project as files, and reports what is still open — see Working with Specifications.

4
Route for e-signature

When the spec is ready, route it for approval. Once it's signed, the Build Agent takes over — see E-signature & Approval.

Configuring your application

Add the environment variables your application needs in the project’s Settings. Use the exact names expected by your application.

Bringing an existing app

You don't have to start from scratch. Point Amira at a Git repository or a folder on your computer and it reverse-engineers a starting specification — requirements, a capability graph, and open gaps — that you then refine like any other spec.

Where to next#