Keep building with Echo

Choose Echo Infra to start building

Echo Infra keeps your projects, build sandboxes, and verification running. Bring your AI provider keys and pay your provider directly.

Back to Echo
ECHO FIELD GUIDE

Make the most of Echo.

Start a project, connect the services it needs, and understand the controls that help protect your workspace.

Read the guides

How to build with an AI app builder

Long-form guides on the method behind Echo: how to brief a build, how to scope a product before you ask for it, and what actually happens between a prompt and a verified project.

Turn an idea into a project

Describe the result you want in the dashboard composer. You can start from a prompt idea, attach reference files, or use voice input. Select Plan to shape the work first, or Build to start implementation directly.

  1. Describe the outcome. Include who the app is for, the main tasks people need to complete, and any visual direction you have in mind.
  2. Choose how Echo runs. Managed mode routes through eligible Echo services. Your providers mode uses supported provider accounts connected in Settings.
  3. Review the project workspace. Follow the build conversation, inspect the preview, and switch to files or code when you want to review the implementation.
  4. Make changes in small steps. Ask for a specific change, then review the updated preview before sharing or deploying.
TipClear requirements make a stronger first build. Mention important pages, key actions, and sample content instead of only naming the kind of app.

Connect the services your project needs

Plugins connect a workspace to services such as payments, storage, source control, and other APIs. Connections are configured from the plugin catalog and are scoped to the selected workspace.

  1. Open Plugins from the dashboard and search or filter the catalog.
  2. Select a provider to read its overview and setup steps. Get its credentials from the provider’s official account settings.
  3. Enter the requested values and choose Verify & connect. Echo checks supported credentials before saving them.
  4. For an API that is not listed, use the add button to configure a custom plugin or an MCP server. You can manage which catalog plugins are available in Plugin settings.
CredentialsPlugin secrets are encrypted before storage, scoped to the workspace, and not shown again after submission. Remove a connection or reconnect it to replace its credentials.

Review project findings and workspace policies

Echo provides project-level security scans and workspace-level privacy and security controls. These settings help teams choose how they share previews, handle sensitive data, and review publishing.

  • Project scans: Open a project’s Security tab to review scan findings and use the available fix actions. The Production Check also runs a security scan with environment, route, and accessibility checks.
  • Workspace policies: Open Settings → Privacy & Security to review controls for invites, MFA, preview sharing, code downloads, secret checks, MCP approvals, sensitive-data warnings, and publishing checks.
  • Provider keys: Add AI provider credentials under Settings → API. Keys are encrypted and are not returned to the browser after saving. A saved key is usable only when Echo has an active adapter for that provider.
Before publishingReview the generated app, confirm its environment variables and provider connections, and address any security findings that apply to your project.