Privacy and Security: Difference between revisions
Jump to navigation
Jump to search
Created page with "Every aspect of the project will follow generally accepted best practices for security. I have a background in information security and from the beginning I designed the infrastructure, database, and application, to adhere to generally accepted best practices for security. I like the idea of making any customized code we write as open source. We might fork off MediaWiki The entire architecture will be build with the following goals * Each user owns their own data and..." |
No edit summary |
||
| Line 1: | Line 1: | ||
Every aspect of the project will follow generally accepted best practices for security. | Every aspect of the project will follow generally accepted best practices for security. | ||
=== Architectural Goals === | |||
* Each user owns their own data and everything is private by default | * Each user owns their own data and everything is private by default | ||
* Within a few years, we plan to have independent audits to validate: | * Within a few years, we plan to have independent audits to validate: | ||
| Line 14: | Line 11: | ||
* Cost optimization | * Cost optimization | ||
* Automate as much as possible to minimize time required for operational maintenance | * Automate as much as possible to minimize time required for operational maintenance | ||
=== Software License Model === | |||
* If we make our code available open source, we cannot restrict platform usage to non-commercial | |||
Latest revision as of 14:43, 22 June 2026
Every aspect of the project will follow generally accepted best practices for security.
Architectural Goals
- Each user owns their own data and everything is private by default
- Within a few years, we plan to have independent audits to validate:
- Technical: application, source code, infrastructure, multi-tenant isolation
- Resiliency: data privacy, backup and disaster recovery
- Procedural: SOC 2, ISO 27001
- Infrastructure should be able to scale to 100,000 users
- Use open source technologies whenever possible
- Cost optimization
- Automate as much as possible to minimize time required for operational maintenance
Software License Model
- If we make our code available open source, we cannot restrict platform usage to non-commercial