Echo / Build with AI
Build apps with your own AI API keys.
Echo is a BYOK AI app builder for web apps: describe your project, review a plan, build and preview it, and keep the source code. Your provider bills AI usage separately.
What BYOK means when building an app
BYOK means bring your own key: you connect an API key from an AI provider, and Echo uses that provider to help plan and generate your project. The provider bills the model usage to your provider account. Echo’s workspace and build infrastructure are a separate part of the cost.
This is different from adding an AI chatbot to the app you are building. A key used by Echo to generate code does not automatically configure an AI feature inside the generated app. That feature needs its own server-side integration and billing decisions.
Estimate the complete cost before choosing a plan
Budget for three separate costs: Echo’s plan, the AI provider’s usage charges, and the services used by your finished application. Database, email, payments and hosting can have their own limits or charges. A free builder trial does not make provider API usage free.
Echo adds no token markup to BYOK usage. Check the current pricing page for workspace limits and availability. Start with a small project and a provider spending limit; compare the provider’s actual bill with the number of useful changes you completed. A large context, repeated build attempts and repair passes can consume more tokens than a short prompt suggests.
A practical first-build workflow
Connect a supported provider in your Echo workspace. Choose a model that is available to your account, confirm that API billing is enabled, and keep the provider’s spending controls in place. An unavailable model, exhausted quota or rate limit can interrupt a build.
Describe one complete workflow and use Plan to review the screens and data before building. Then build, inspect the preview, and request a single focused change. Export the source or sync it to GitHub when you are ready to continue elsewhere. Source ownership does not replace a review of dependencies and their licences.
Keep generation keys separate from application secrets
Never put provider keys in a public prompt example, a screenshot, a Git repository or browser code. For an AI feature in your finished app, keep the secret on the server and call it through an authenticated endpoint with usage limits. Review exported files and environment configuration before publishing.
Rotate a key at the provider if it is exposed. Restrict the replacement key where the provider supports it. Choose the provider and model with your project’s data requirements in mind; BYOK does not mean inference runs locally or that the provider receives no data.
When BYOK is a useful fit
BYOK is useful when you already manage provider accounts, want to choose among supported models, and prefer a separate provider bill. It requires you to manage keys, usage and quota. Evaluate that work alongside infrastructure cost and the quality of the generated result.
Before committing to any app builder, test source export, inspect a real generated project, try an error case in the preview, and check what remains usable if you stop subscribing. Those tests tell you more about portability than a promise of “no lock-in”.