Portability
Leave if you want
ProsperApps should never need data captivity to keep customers. Interoperability and exportability are part of the product expectation.
About ProsperApps
A SaaS company designed around different incentives.
ProsperApps exists to develop and run a portfolio of SaaS products, and to selectively build SaaS for third parties, under a model that rejects lock-in, invasive data practices, dark patterns, and extractive ownership structures. SaaSpawn is the method we use to make that model operational.
What the company is for
A foundation-aligned product company with room for bespoke work.
- ProsperApps develops and operates its own suite of SaaS solutions in both existing and emerging market segments.
- The SaaSpawn method is how we design, ship, and operate those systems across shared platform seams and product lines.
- Every ProsperApps solution is expected to align with the Prosper Foundation Declaration rather than merely borrowing its language.
- We can also build and maintain SaaS for third parties, but only when the resulting service can honestly satisfy the declaration commitments.
- The company is intended to remain a foundation-owned operating business rather than a vehicle for private shareholder extraction.
What that means for customers
The business model and the product model are supposed to reinforce each other.
If the company is truly foundation-owned and declaration-aligned, then portability, privacy, healthier UX, and long-term product quality stop being nice words and become part of the actual operating logic.
Privacy
Data minimization by design
We aim to collect the least information genuinely required to provide a strong service, not the maximum amount that might later become useful for extraction.
UX
No manipulative growth theatre
We want product patterns that are healthy, legible, and beneficial rather than engineered pressure systems designed to hijack judgment.
Quality
No planned decline into enshittification
The goal is to maintain and improve quality rather than degrade it to serve some unrelated optimization target.
Primary role
Public company surface Frames the company, declaration, careers, and solution portfolio for external readers.Supplement mode
Formulaic disclosure block This data is intentionally rendered next to the existing About narrative rather than replacing it.Shared stewardship
Prosper Foundation
ProsperApps is intended to be fully owned by the Prosper Foundation. That means the company site should explain not only what the company says it believes, but also which open-source components and standards shape its public web presence.
Declaration
Declaration and commitments
This disclosure block supplements the existing company narrative with the more formulaic dependency and standards view required across the ecosystem. It is meant to coexist with product-specific and company-specific About copy.
Disclosure rule
Why this appears after the narrative sections
The company-specific About content stays intact. This shared block adds a consistent provenance layer so readers can see licences, standards, and contribution paths without collapsing the original narrative into a generic template.
Licences & standards
External dependencies, derived assets, and open standards
Every item should link to the relevant licence file, project page or repository, and contribution path so provenance and participation stay visible.
Application stack 5 items
Core open-source stack used to build and host the public company site.
Resource
Svelte
Component runtime for the public company pages.
Resource
SvelteKit
Routing and app-shell framework for the company site.
Resource
TypeScript
Typed site metadata and content structures.
Resource
Vite
Development and build tooling for the site.
Resource
Wrangler
Cloudflare deployment tooling used for hosted releases.
Open standards 3 items
Web platform standards used directly in the company site shell and its shared visual system.
Resource
Fetch Standard / CORS
Basis for browser networking and preview-friendly API access patterns.
Resource
CSS Custom Properties
Used for shared design tokens and theme variables across the site.
Resource
SVG
Used for brand assets, icons, and vector-based decorative elements.
Next step