Building, infrastructure, security, plans, and your account.
JavaScript. Choose React, Vue, or vanilla JavaScript, and Lambot scaffolds the project from your description. A full npm package manager runs in the browser, so the libraries you would normally reach for are available right away.
Your functions run on AWS Lambda, so AWS Lambda's runtimes are what you have to work with. Python and JavaScript have first-class dependency management built into the editor — pip and npm, both in the browser, with no local build environment to maintain. You can also publish reusable layers to share versioned dependencies across functions.
GitHub and Bitbucket. Connect either one and work with real Git on each function: branch, diff, commit, history, pull, and merge.
LambdaDeploy keeps the three places your function really lives — your workspace, your deployed function, and your Git branch — reconciled with each other, so a change made somewhere else while you are editing is surfaced rather than lost.
Yes, on paid plans. MCP access lets you connect Claude or another MCP-capable AI client directly to your LambdaDeploy environment, so you can work with your applications, functions, and data from the AI tools you already use.
Native AWS. Lambda and API Gateway for compute and APIs. DynamoDB, RDS, and Aurora for data. S3, SQS, SNS, Kinesis, and schedules for events. Your frontend publishes to a live URL with custom domain support and automatic SSL.
Your application talks to AWS services directly, as any AWS application does.
Yes. Connect one or more AWS accounts and work across multiple accounts and regions, switching context deliberately from any screen. Everything you build is created in your account, and your LambdaDeploy subscription is billed separately from your own AWS usage.
The AWS environment we run, so you can start building the moment you sign up without connecting an AWS account of your own. Every plan includes it.
When you are ready to build in your own AWS account instead, connect it and carry on — your work moves with you.
Lambda Deploy Cloud is covered by your credits, so there is no separate AWS bill to set up or settle.
Any AWS account you attach is your own, and AWS bills its owner directly for what runs there, exactly as it does for anything else in that account. Your LambdaDeploy subscription stays separate from that.
They scale the way AWS applications scale, because that is what they are: native code on native AWS services, running in your account under your configuration.
LambdaDeploy is where you build and operate the application. Once it is live, AWS serves your users directly, so your ceiling is AWS's ceiling.
Your code lives in your own AWS account and your own GitHub or Bitbucket repositories. We operate on your infrastructure rather than holding your running application on ours, and every connection uses credentials you supply and can revoke at any time.
Anything stored on our side is encrypted at rest with keys that belong to your account alone.
Inside the workspace, safety is structural. AI changes arrive as reviewable diffs for you to approve. Backend resources are surfaced for your approval before they are created. Data writes require explicit confirmation. Data-loss guards protect work you have not saved yet.
No. We use commercial-grade LLMs, and your code is never used to train models or to build code for anyone else. What you write stays yours.
Free accounts include a daily credit allowance that refreshes every day. Current allowances are on the pricing page, and signing up is free.
Free credits refresh daily rather than accumulating, so every day starts fresh.
Yes. Unused credits on a paid plan roll over, so a quiet month carries forward into a busy one.
Credit packs you purchase stay available far longer than a monthly allowance, well past a single billing cycle. The pricing page has the current terms.
Cancelling returns your account to the Free plan rather than closing it. Your applications keep running and your data stays where it is.
Custom domains are removed, so an application served on your own domain goes back to its LambdaDeploy URL.
Anything running in your own AWS account carries on as before, because it belongs to your account rather than to your subscription.
We delete your Lambda Deploy Cloud environment and all of your data with it.
Anything you built in your own AWS account stays exactly where it is — in your account, in your repositories, under your control.