Airship is a Content Management System designed to provide a secure foundation for your website.

Why Airship?

Carefully Chosen Cryptography Features — Powered by the Sodium cryptography library (accessed through Halite, our easy-to-use libsodium wrapper).

— Powered by the Sodium cryptography library (accessed through Halite, our easy-to-use libsodium wrapper). Secure Automatic Updates — Critical security updates will automatically be applied within an hour (in the default configuration). Never worry about something like this happening again.

— Critical security updates will automatically be applied within an hour (in the default configuration). Never worry about something like this happening again. Open Source — Airship is dual licensed. You can use it under the terms of the GNU Public License as Free Software, or if you'd prefer, you may purchase a commercial license from Paragon Initiative Enterprises.

— Airship is dual licensed. You can use it under the terms of the GNU Public License as Free Software, or if you'd prefer, you may purchase a commercial license from Paragon Initiative Enterprises. No Legacy Cruft — Airship was born into PHP 7 and does not need to retain the bloat or bad designs necessary to maintain compatibility with early versions of PHP 5.

Frequently Asked Questions

Why does the community need yet another CMS?

Airship carries two benefits that none of the existing content management system solutions offer:

Airship was designed, and is maintained, by a team of PHP security experts. Airship is not encumbered by risky backwards compatibility concerns and years of technical debt.

Though our security team often shares our insight into better security practices with the maintainers of popular Free Software projects, they are almost always held back by technical debt and obligations to maintain compatibility with legacy systems.

What makes Airship different from any other CMS?

The short answer: In terms of security, Airship is worlds apart from the CMS platforms you're already familiar with.

The Long Answer:

A lot of the security problems that the other CMS solutions encounter is the result of unknown unknowns. For example, "Is it safe to pass user-provided data to unserialize() in a PHP 5 application?" is a question that many CMS developers would never even think to ask (let alone know the answer to off the top of their heads).

We live and breathe application security. Our set of unknown unknowns is consequently a lot smaller than most PHP programmers'.