We want to write good software. We believe that good software is both a joy to our developers and customers. Good software should:

• not be demanding. Good software exists to serve, not to make requests. We follow the Convention over Configuration pattern wherever possible to help you and your customers get things done quickly and without knowledge about technical details.
• save your time. Good software should be fast, concise and easy to use. We have designed nepal with accessibility in mind: long-lasting login sessions, mouse-free forms, no image bloat and easy screens with fast CSS. nepal gets out of your way to save time and money.
• be sustainable. Good software should not only exist now but also in the future. We have built nepal with a very clean code base that is easily extensible and standards compliant. We have used a multitude of third-party libraries, applications and standards to make nepal usable and sustainable.
• be non-invasive. Good software should not infiltrate your system. nepal deployment is designed to integrate well by using system packages, configuration conventions and FHS compliant installation paths. Our deployment tools are fast, non-interactive and idempotent to facilitate easy installation and upgrades. No lost configurations, no downtime, no upgrade nightmare.
• anticipate your needs. Good software should be designed for its users. We have seen most other management products and surrendered at some point. nepal is built with both administrators and customers in mind.