PLATFORM
Platform Principles
These are the enduring ideas behind how Simpleasyty builds software. They are written for enterprise reviewers, not for developers, and they are meant to stay true even as the product evolves.
IN PRACTICE
How the principles guide decisions
The principles are not a separate policy layer. They are practical checks used when deciding how a feature should be built, what it should access, and how it should evolve.
Product decisions
When two approaches can achieve the same outcome, we prefer the one with fewer moving parts and the closer fit with Atlassian's native capabilities.
Data and permission decisions
We consider what information and access a feature actually needs, then avoid collecting, processing, or requesting more than that purpose requires.
Long-term decisions
We favour changes that remain understandable, can be explained publicly, and can be maintained without making the product harder for customers to review.
What this means for customers
These principles are why the product aims to stay calm, predictable, and easy to approve. They guide how we make decisions about product design, data handling, and long-term changes.
For the practical architecture behind the product, seeArchitecture. For how the product behaves over time, seeReliability. For customer data protection, seeSecurity.