FAQ

Open the category catalog or search. OS/runtime and version filters appear when enabled in settings. The home page shows New and Popular blocks.

Each card lists supported distros (e.g. Ubuntu, Debian, CentOS, Docker) and OS versions. Check the badges on the card — there is no universal “any Linux” promise.

To limit download abuse and keep favorites tied to you. Public card descriptions are open; files and extra materials require sign-in and verified email when enabled on that material.

On the material page use Get materials / download after sign-in and email verification. Updates are published by the operator — check the version and date on the card.

Yes. Core published materials are free under the sign-in/email rules. Paid tiers may come later;

RunStack owns its own copy and UI. Code, images, and third-party projects keep their authors’ licenses. Always check upstream and the card / terms of use.

Check the FAQ, then open feedback with steps, a screenshot/log, distro, and OS version. We will help when we can — this is not a commercial support SLA.

Under Utilities: DNS Checker, SSL/TLS Checker, subnet calculator, Cron, HTTP Inspector, Port Checker, Email DNS Checker, IP/ASN Lookup, and Webhook Tester. Use them to check DNS, certificates, network, mail, and webhooks without installing software.

Check results are not published or indexed. Analytics (unless you opt out) records that a tool was used — not the domains/IPs/payloads you entered. Temporary webhook inboxes keep events for a limited time (about 24 hours), then delete them.

Only public targets are allowed (no private networks). Rate limits apply, and some features may be temporarily turned off under load or maintenance. If Utilities are unavailable, try later or open feedback.

Create an inbox, paste the public Receive URL into your service, and keep the Manage token yourself — it is shown once. Events appear in the list; you can configure the response, compare payloads, verify signatures, and safely replay. The inbox expires in about a day.

Use [feedback](/feedback) after sign-in: name the utility, what you entered (no secrets), expected vs actual behaviour. You can reply in the ticket and mark it Resolved or Rejected when done.