We believe in being open where it matters most. Our core platform is open source, reflecting our commitment to the developer community that has helped build Avalonia over the past 11 years. We maintain transparent technical documentation and pricing, ensuring our users and customers can make informed decisions.
Internally, we practice radical transparency. All team members have access to our financial information, including revenue numbers and cash position, shared through quarterly all-hands meetings. We believe this level of openness creates trust and enables better decision-making across the organisation.
We're committed to honest conversations, even when they're difficult. We'll say no to customer requests that don't align with our vision or technical reality. We're open about the challenges of building a sustainable business around open source software. While others might obscure truth to win short-term deals or appear more successful, we choose transparency, even when it's uncomfortable.
This commitment to honest communication builds trust with our community, customers, and team members. We believe this trust is more valuable than any feature we could build or deal we could win. It's the foundation of our long-term relationships and success.
"It's done when it's done" isn't just a saying, it's how we work. We take pride in our craft and refuse to ship anything we wouldn't be proud to put our names on. While we're responsive to business needs, we don't let artificial deadlines compromise the quality of our work.
Our customers are developers like us, and we know they value reliability over rapid releases. Being first to market with a feature doesn't matter: being better does. While competitors might race to announce new capabilities, we focus on delivering robust, well-engineered solutions and let the solutions talk for themselves rather than focus on flashy marketing.
We balance this by encouraging regular iteration and feedback, but never at the expense of stability or quality. Our reputation is built on excellence, not press-releases, and we're proud to take the time needed to get things right.
Our platform is built by developers, for developers. While not everyone needs to be a software engineer, we expect all team members to be technically literate. This means being comfortable with basic developer tools like Git and Markdown, understanding our users' needs, and being able to contribute to our technical discussions.
This shared technical foundation helps us better serve our community and maintain our high standards for quality.
We believe in hiring exceptional people and giving them the autonomy to do their best work. Rather than implementing rigid processes, we foster an environment of trust and open feedback. We expect team members to identify high-impact opportunities and pursue them independently.
Performance is judged on impact and quality of work, not adherence to processes or plans. We encourage direct, constructive feedback while maintaining respect for each other's expertise and judgment.
We value people who see opportunities and take action. If you notice something that could be better, whether it's in our code, our processes, or our customer experience, improve it. We trust our team members to act with an owner's mindset, making decisions and taking initiative to enhance any aspect of our business.
No one will ever be reprimanded for thoughtfully trying to improve things. We encourage calculated risks and learning from both successes and failures. This might mean refactoring code that's becoming difficult to maintain, streamlining an internal process that's creating friction, or enhancing documentation to help our users be more successful.
Impact comes in many forms. Sometimes it's major architectural improvements that make our products more robust. Other times it's small but meaningful enhancements to the developer experience. What matters is the outcome: did we make something better for our users, our team, or our business?
This bias for impact means: