hStatus: An open source status page you can host on S3
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


hStatus - Open Source Static Status Page

hStatus is an open source status page designed to be hosted on AWS S3 as a static site. It requires no servers to operate, and when combined with your favorite CDN, you should be able to host a highly available status site for minimal cost.

Together with Hiram Pages, you may update incidents using only a web browser. Without Hiram Pages, editing incidents is as easy as editing JSON files.


A live demo with sample data is at https://status.hstatus.com

Other Hiram Software projects like Hiram Pages and Monday Wire have used hStatus for some time.


All the benefits of...

  1. A static website -- no servers to cause downtime or security incidents
  2. AWS S3 -- complete control of your data, highly available, and inexpensive
  3. Open source -- fork and modify to suit your needs
  4. Hiram Pages -- log in to update your incidents
  5. Markdown-formatted posts

With a few drawbacks...

  1. Realtime data graphs not yet implemented
  2. Incident archive not yet implemented
  3. Not a trendy VC-funded startup


  1. AWS S3 Bucket configured to host a static website (see below for sample bucket policy)
    1. There are many good references available via your favorite search engine with specific instructions on how to use AWS S3 to host static websites.
  2. If you would like to administer hStatus from the internet, you will need Hiram Pages


  1. Create an AWS Bucket to host your status page. Say, status.example.com
  2. Download the dist package from releases or build yourself using:
    1. npm install

    2. jspm install

    3. gulp dist

    4. (that's it)
  3. Using your favorite method, upload the dist folder to your AWS bucket.
    1. I like to use the AWS CLI, and a sample script is available in ./publish.sh
    2. Configure the bucket to host a static website. A sample policy is below for convenience. Update your DNS to point to your bucket.
  4. Then add incidents.
    1. Easy method: go to Hiram Pages, configure Hiram Pages for your AWS Bucket, and create an hStatus link.
    2. Edit the current.json file manually to add in incidents. You may have to create it.

All of your data is hosted on your AWS Bucket. You have complete control of your status page. Your page will only go down if AWS S3 or your DNS provider goes down.

If you choose to save your hStatus link in the settings, you will be able to log in to your hStatus page using the admin.html, whose link is at the bottom of the index page.

Developing and Building

You need JSPM, NPM, and Gulp to develop hStatus.

This project is based on the ES6 AngularJS Starter, also available from Hiram Software.

  1. Have your bucket name and Hiram Pages Link ready
  2. git clone https://www.github.com/hiramsoft/hstatus
  3. cd hstatus
  4. npm install
  5. jspm install
  6. gulp serve
    1. Go to http://localhost:8080 to develop
  7. gulp dist
    1. Minifies the JavaScript

Note: CORS will be an issue during the development because of how AWS S3 responds with CORS responses between http://localhost and https://aws... If this blocks you, you can disable CORS in Chrome:

open /Applications/Google\ Chrome.app/ --args --disable-web-security

Obviously, you should only use this feature when developing sites that have CORS interaction issues and not browse the internet with web security disabled!

Contributing and Filing issues

Pull requests are welcome. Two requests:

  1. All contributions must be made under the GPL V3. Please add your name to the CREDITS file to signify you agree.
  2. Err on the site of troubleshooting or fixing yourself :)

Sample Bucket Policy

The following is a sample policy for your bucket that allows the general public to view your status page

      "Version": "2012-10-17",
      "Statement": [
              "Sid": "StmtStaticWebsite",
              "Effect": "Allow",
              "Principal": "*",
              "Action": "s3:GetObject",
              "Resource": "arn:aws:s3:::[your-bucket-here]/*"

Sample Editor Policy

Hiram Pages knows how to generate a default link that lets editors manage incidents.

You want to make sure that the Role policy allows reading, writing, and listing of files on your bucket.


  • Usage graphs
    • I am investigating how AWS Lambda + AWS Cloudwatch may be useful to generate usage graphs.
    • I think it's possible, and if so, this would enable you to have pretty real-time pictures
    • Would also enable calculating an SLA automatically
  • Archiving old incidents
    • This is a feature that people say they want, but I've never seen in practice this be a deal breaker.
  • Mobile layout tweaks
    • I picked default a Zurb Foundation layout for the admin interface, and it isn't quite right on my iPhone. Nothing blocking, but it could be better.