For companies
Appys shows each app’s status and record using only what the company itself publishes. Here’s what that means for you, what we’ll gladly fix, and what no one can buy.
We read your official status page, the same one your customers can see, and show what it says. If another official page covers your app, such as one dashboard for several products, we name that page instead. We don’t test your app ourselves and we never guess. How Appys checks apps.
Your record is the list of problems your status page has published, with when each started and finished. A problem only counts as a major outage when your own page says the whole service is down, for example a critical incident, or every part marked down. One part down is “some problems”. Planned maintenance never counts as a problem, and problems your page limits to one region or a few customers are shown separately and left out of the totals.
Each app page compares your record with apps that do the same job, using what each one reports on its own status page. It also gives credit for keeping people informed: listing your separate parts, posting regular updates, and saying what caused a problem. A status page that reports small problems openly is a good sign, and we say so next to the numbers.
No payment, partnership, affiliate deal or advert changes a status, a record, a comparison, a ranking or a category leader. They follow the same rules for every app.
Some links on Appys are partner links, explained on the How Appys makes money page linked at the foot of every page, and adverts are labelled. In the alternatives boxes, when several apps are equally close matches, partners may be listed first. That’s the only place a partnership affects the order of anything. How Appys makes money.
We add apps that people look for and that publish a public status page we can read. Fill in the form with your website, what the app does, which apps it’s an alternative to, and the address of your status page. The form checks we can read it there and then, and you confirm with one email from your company address.
We read status pages run on Atlassian Statuspage, Instatus and Better Stack. If you don’t have one yet, Instatus has a free plan, and we can read its pages straight away. Once listed, your app has its own page and can appear as a working alternative on the pages of apps that do the same job. If you run an affiliate or partner programme, you can tell us on the form. It’s optional and doesn’t affect whether we list you.
Email [email protected] from your company’s own email address with the subject Claim followed by your app’s name, for example Claim Zendesk. We check the email really came from your company’s domain, then reply to that address with a private link. There you can confirm your description, add links to your help centre, developer docs and status updates, point us to the right status page, and tell us about anything we’ve got wrong.
We check every change before it goes live, and your page then says its details were confirmed by your company. None of it can change your status or record.
Our reader names itself AppysStatusBot and only reads the public feed your status page offers. It reads it when someone opens your app’s page on Appys, but never more than once every 2 minutes. Otherwise it reads it every 30 minutes, or every 2 to 5 minutes while you have a problem or people have asked us for email alerts about you, plus your history every 6 hours. If your status page turns automated readers away, we stop reading it and link to your page instead. If you’d like our reader let in, or read less often, tell us.
For anything else, email [email protected] from your company’s own email address, so we know it’s really you. We only ever reply to the address that wrote to us.
