All your AWS clients in your panel. Each client, only what they need in theirs.

No. You sign up with your email (or with your Google account) and get 15 days with everything your plan offers, with no card and no commitment. Nothing is charged automatically when it ends.

Yes, and it's simple: if you pay for the whole year you pay for 10 months and the other 2 are free, on any plan (49, 120, 390, 1,490 € a year depending on the plan). In the plans table you can see the monthly or the yearly price with the selector above. No commitment beyond the paid period.

The account is paused: you can't sign in, but nothing is deleted (your keys, machines, users and activity stay where they are). If you want to continue, write to us and we will activate your plan; if not, you don't have to do anything. Card payment from within the app will arrive in a later phase; for now we arrange it with you by email.

No. Nothing. No agent, no program, no script. Simplio talks to your cloud provider through its official API, with an access key that you create yourself. Your machines don't even know Simplio exists. In fact, this is one of the reasons our customers choose us.

The key you register only allows what you have given it permission for: viewing status, starting, stopping, touching the firewall or managing a bucket. With those permissions it is not possible to get into the machine or read its disks. The exception is the Lightsail terminal in the browser, and it is worth knowing exactly how it works: it is only possible if you add the optional "Terminal" block to the key (permission lightsail:GetInstanceAccessDetails, with which AWS hands over a temporary SSH key valid for a few minutes, the same one its web console uses); inside Simplio it can only be opened by a user to whom the administrator has given the "terminal" action and that specific machine, and always with the two-factor code; the session goes through the Simplio server, which does not record it, and every opening is logged with user, machine, date and IP. If you don't want anyone to be able to get into your machines from Simplio, don't add that block to the key: without it, neither your users nor Simplio can do it. The key is stored encrypted with a master key that is not in the database: only the Simplio server decrypts it, at the moment of talking to AWS, and it is never shown on screen again. As with any service, the Simplio operator has technical access to the server; what really protects you is that the key can only do what you decided, and that you can revoke it in AWS whenever you like.

There are no recovery codes or email shortcuts: that way a stolen password is no use for getting around it. If you are a regular user, your company administrator can switch off your two-factor from Users, after making sure it is you through a channel they know (a call, in person); that action is recorded in the activity log and you set it up again on the new phone when you sign in. If the one who loses the phone is the administrator and there is no other administrator in the company, the Simplio operator does it, only after verifying the identity with the company by a means other than email, and that is also logged. We recommend always having two administrators. In the meantime nobody can sign in with your user, which is exactly what you want.

Yes, with both. Lightsail machines also have the built-in firewall, the terminal in the browser and metrics; EC2 ones have metrics through CloudWatch. Both support snapshots. You can mix them on the same screen. S3 buckets, Lightsail and RDS databases and Lambda functions are also supported.

Yes, if they are written in Python, Node.js or Ruby: you open the function, change the code in the editor, save it confirming with two-factor and test it right away, seeing the response and the logs. In other languages (Java, .NET, Go) the function can be viewed and tested, but the code is not edited from Simplio, because it has to be compiled. You can also create new functions (Python, Node.js or Ruby) with a button, with sample code to get started, and give them a public URL with one click.

Yes, if the domain is in Route 53 (Amazon's DNS). Each domain is a card with its records: you see where the website points, which server receives the email and the verification texts, and you can add, change or remove A, AAAA, CNAME, TXT, MX, SRV and CAA records with a single line and help depending on the type. The records that make the domain work (NS and SOA), aliases to other AWS services and those with a routing policy can be seen but not touched; removing a record asks for two-factor and replacing an existing one or touching the root asks for confirmation, because a badly set record can leave a website or email without service. Creating new domains, alias records and health checks will come later.

Not yet, they are in development. The application is already prepared inside for several clouds, so when they arrive you will have the same screen and the same permissions. If you have machines on Azure or Google and you are interested, tell us: it helps us prioritise.

Under an hour. Creating the key with minimum permissions in AWS takes two minutes with the script that the help generates for you (you paste it into the AWS terminal and it gives you back the key); if you prefer to do it by hand, it explains it step by step. After that, registering the key, choosing machines and creating users takes a few minutes. If you prefer, on the Empresa plan we do it with you.

Yes, and in great detail. Per user you decide whether they can view, start, stop or restart, create snapshots, handle files or databases, open the terminal, and whether two-factor is required. And per object: which machines, buckets or databases they can access, either by giving them a whole key or just individual objects. The typical case is that the manager sees everything and a collaborator only one machine.

Yes, and it is one of the most used features. You create a user for your client, assign them their machine and tick what they can do: reboot, add or remove their IP in the firewall, take a backup. They log in with their password and two-factor code, see only their card with those buttons and never see your AWS key or the other accounts. You also decide whether they see the costs of their machines or not. Everything they do is in the activity log. If they stop being a client, you deactivate them.

Only those for the actions you want to use: listing machines, seeing their status and metrics, starting, stopping and restarting, reading and changing the firewall, creating and deleting snapshots and, if you use them, managing the buckets or databases you choose. No billing, no creating or deleting machines, no other services. In the help you tick boxes for what you want to allow (view only, no firewall, a single region…) and it generates the policy and the script for you.

With the role-based connection there is no key to leak: Simplio asks AWS for temporary credentials every time and they expire in an hour. If you use a classic access key: first, it is encrypted and never shown again, so leaking it from Simplio is very difficult. Second, since it has minimum permissions, whoever had it could neither create machines nor see your billing; they could do the same as the key allows in Simplio (stop a machine, delete a file from a bucket if you gave it that permission, open the terminal if you added that block), and that is why each key should only be given what it needs. And third, you revoke it in your cloud in a minute and create another. The activity log also tells you whether anyone did anything strange from Simplio.

Yes. There is no commitment and we leave nothing installed. You delete the access key in your cloud and your machines stay exactly as they were.

Yes. The Costs screen shows, for each AWS account, what has been billed this month so far, the end-of-month forecast and last month, exactly as AWS itself gives it (Cost Explorer), in dollars and in euros. Next to it, an object-by-object estimate using the public rate, so you know how much each machine or database costs per month. And if you want, a budget per user: what each person can create from Simplio has a cap.

Yes, by email and in the app itself. Simplio checks your accounts every 15 minutes and warns you of a stopped machine that should be on, a copy that has not been made, a domain or email identity that is expiring or is no longer verified, a budget that is exceeded or an email bounce rate that is too high. Each person chooses which alerts they want to receive, and Simplio doesn't nag: one alert when it appears and another when it is resolved.

Yes. You can schedule snapshots for each machine (every day, every week…), say how many are kept and, if you want, copy them automatically to another AWS region, so that a problem in one data centre doesn't take the copies with it. And before touching anything delicate, a manual snapshot with a button.

Yes. The Email (SES) screen shows your verified domains and addresses in each region, tells you which DNS records are missing (DKIM, SPF, DMARC, MAIL FROM) and, if the domain is in Route 53, adds them with a button. You see the daily quota, how much has been sent, the bounce and complaint percentage, and the suppression list. You can also request from Simplio, via AWS, to leave the testing mode (sandbox).