Ian and Paul are indie developers building privacy first tools for small teams. Their collaboration focuses on transparent pricing, open roadmaps, and community driven product decisions.
Together they run a lean studio that ships practical SaaS apps without aggressive marketing. This article explores their projects, priorities, and the details that matter to users and contributors.
| Name | Role | Primary Focus | Public Profile |
|---|---|---|---|
| Ian | Founder, Lead Engineer | Architecture, security, and developer experience | @ian on GitHub and Bluesky |
| Paul | Co founder, Product and Design | UX, pricing, and customer research | @paul on LinkedIn and Threads |
| Studio | Joint venture | Building and maintaining privacy focused SaaS | studio.example.com |
| Audience | Small teams and indie makers | Tools that are affordable, observable, and respectful | Community forum and changelog |
Core Product Principles
Design and Usability Standards
Ian and Paul prioritize calm, focused interfaces that reduce cognitive load. They ship with real user telemetry and iterate slowly based on qualitative feedback.
Privacy and Data Governance
End to end encryption, minimal data retention, and clear explanations of what is stored are non negotiable. They publish transparency reports and welcome external audits.
Roadmap and Open Development
Public Backlog and Milestones
Their public roadmap breaks work into small, testable milestones. Each item includes success criteria, estimated effort, and context for why it matters.
Community Contributions
They label beginner friendly issues, merge well written pull requests, and document contribution workflows. Maintainers respond to RFCs and design questions within a week.
Architecture and Engineering Practices
Reliability and Observability
Ian focuses on building systems that fail gracefully, with structured logging, alerting, and runbooks. Test coverage, staging parity, and regular incident reviews reduce production risk.
Security and Compliance
Regular dependency audits, signed releases, and least privilege deployments are standard. They document threat models and provide compliance guides for enterprise customers.
Business Model and Pricing
Transparent Plans and Fair Usage
Plans are simple, with clear caps and migration paths. Usage based billing is explained up front, and overages are handled with generous buffers or clear upgrade prompts.
Sustainability and Growth
Reinvestment focuses on tooling, documentation, and support rather than rapid headcount growth. The studio explores grants, sponsorships, and ethical partnerships aligned with their values.
Steady, Responsible Growth
Their approach blends sustainable engineering, clear pricing, and community minded development.
- Ship small, testable changes with measurable outcomes
- Maintain strong privacy and security standards across the stack
- Invest in documentation, observability, and user support
- Engage the community through open roadmaps and RFCs
- Balance growth with long term maintainability and team wellbeing
FAQ
Reader questions
How do Ian and Paul decide which features to build first?
They prioritize based on user interviews, support tickets, and telemetry, favoring changes that unlock broad value and align with their long term product principles.
Can small teams self host their tools if needed?
Yes, many features are available in self hosted editions, with detailed deployment guides, Docker images, and infrastructure as code templates for on premises environments.
What happens to customer data if the studio slows down or closes?
They commit to data export tooling, open source core components where possible, and clear exit paths that let customers move their workflows without lock in.
How often do they release new versions of their products?
They follow a rolling release cadence with weekly patches and monthly minor releases, each accompanied by changelog entries and migration notes.