The questions that come up first.

No. You need something that already works, however you made it. If you can connect a GitHub repository or put the files in a folder, that is enough. Everything a running tool needs around it gets built for you.

Those links are good for showing someone what you made. A tool your colleagues depend on needs more than that: its own storage that is backed up, sign-in with the work accounts people already have, an address that does not change, and every version kept so you can go back. That is what easythings builds around whatever your team made.

Yes, and it is the same product either way. Either easythings builds inside the cloud account your organization already owns, where the data never leaves your control and the cost lands on the bill you already pay, or it provisions cloud for you and hands you an address with nothing to set up on your side. You choose once, at the start.

Those are builders. They help you make the tool. easythings starts after that, and it does not care how you made it, whether by hand, from a template, or by asking an AI. What it provides is the infrastructure underneath: somewhere to run, an address, a sign-in, storage, backups and versions. If you need help building, use a builder. If you have built something and cannot get it in front of anyone, that is this.

Your tool stays your code, in whatever language your AI assistant wrote it in. easythings does not need a special format to run it, and if it runs in your own cloud account, the resources it creates are in your account and visible to you. Leaving means running the tool somewhere else rather than building it again.

Internal tools people open in a browser: forms, approvals, dashboards, small trackers, reports and jobs that run on a schedule. It is built for tools used by people inside your organization, not for products you sell to customers.

Not yet. Today a tool runs on the data it holds itself, which covers forms, trackers and approvals, but not anything that has to read from your HR system or your CRM. Calling your internal APIs, receiving webhooks, holding your keys, and running on a schedule are all being built. If one of those is what decides it for you, say so in the demo, because that is how the order gets set.

Team covers up to 20 users at €10 per user a month, and Business starts at 10 and covers up to 50, at €12 per user a month; either saves 20% billed annually. Both cost the same whether you run in your own cloud account or in cloud we provision, since only who pays the underlying cloud bill changes. Enterprise is sized per organization and priced on request.

Tools stop serving at the end of the term. Before that you can export the data people entered, the history of every deploy, and the code itself. If it was running in your own cloud account, the resources are already yours and stay where they are. We delete nothing while the export window is open, and the contract states how long that window is.

In your own cloud account, it never leaves, the same as any other resource you run there. In cloud we provision, it stays in the region you pick, inside the European Union, isolated from every other organization we run. This site's privacy policy covers what we collect through the demo form itself, which is separate from what your tools hold.

The tool is not tied to their account. Bringing a tool in and being allowed to change one are permissions given per team, not personal ownership, and the record of every version published stays whether or not they are still around to look at it. Whoever has that permission next picks it up exactly where it was left.

Nothing here cares how the code came to exist. Written by hand, from a template, by a different assistant, or by you finishing what an AI left half done, easythings runs it the same way: there is no format to convert to and no framework to adopt first.

Every version you publish is kept, not just the latest one, so putting yesterday's back is one click rather than a rebuild. The record also shows exactly what changed and when, so finding out what broke it does not start from guessing.

In your own cloud account, the resources easythings creates land on the cloud bill you are already paying, the same as anything else running there, and easythings itself is billed separately, per your plan. In cloud we provision, there is just the one bill, from us, and no separate cloud account to manage or pay.

Only what it needs to create and run the pieces described on this site: somewhere to run, an address, sign-in, storage and backups. Every resource it creates is visible to you in your own console, the same as anything else in the account, so nothing is set up out of sight.