My Idlers Hosting

Open your pod URL and use the Create one link on the sign-in page to register your account. If you already have an account, sign in instead. Start by adding a service, such as a server or domain, with its provider, price, payment term and next due date.

The project README describes the supported service types and settings. Account registration can be limited by the deployment's configuration, so a registration link is not a promise of unlimited user accounts.

No. PikaPods sets up and runs My Idlers for you, including OS and app updates and HTTPS. You won't touch Docker or a server.

Run YABS on the separate server you want to benchmark, then add its output to the matching server record in My Idlers. Hosting the inventory does not benchmark your other machines automatically; you need access to those machines to run the benchmark.

YABS can also send its results directly to My Idlers using the server record's ID and your account's API key. Follow the YABS instructions, and keep the API key private.

Yes. My Idlers has a REST API for its resources. Find your API token on the Account page and use it as a bearer token in requests to your pod's API endpoints. The API documentation lists the endpoints and required headers.

Don't rely on it for that. The README describes the due date as simply a reminder on the dashboard, and doesn't mention email or push alerts. Once a due date has passed, viewing the homepage moves it on by one payment term, so it doesn't record whether you paid. The API returns due dates if you want to build your own alerts.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

Yes. My Idlers is part of our Green Heart program, so part of the revenue from every deployed pod goes to the project.