ChoirPower
Choirs and membership-driven music organizations
A domain SaaS built with the SaaSpawn method for operations, participation, repertoire, attendance, communication, and commercial workflows.
operating
Current and planned solutions
A portfolio model, not a single-product story.
ProsperApps is building and operating multiple solution lines. The SaaSpawn method gives those lines a shared product, platform, identity, mail, and governance backbone so mounted products, shared service seams, and newer calendar, meeting, membership, recovery, or preservation tracks can evolve without collapsing into one monolith.
Operating now
Products and platform surfaces already in motion.
WalletDT, StripeDT, and VippsDT
Digital twin payment, wallet, and integration surfaces
Digital twin replicas of real third-party payment and wallet integrations, used so the ecosystem can develop and test safely in pre-production without depending on live providers. They now also carry hosted checkout-by-session and pay-by-reference pages so product consumers can validate realistic payment handoff behavior against the shared DT plane.
operating
Active build tracks
Mounted product lines and shared service seams under active rollout.
This is where the current implementation work is concentrated: identity continuity, governed mail, encrypted preserve, root-owned product APIs behind the mounted Prosper product fronts, shareable file and preserve handoff flows, and the first calendar and guest-capable meeting slices taking shape beside that backbone.
ProsperSafe
Preservation, secure storage, and controlled file custody
A mounted preservation line with a root-owned encrypted preserve API, ProsperVault-backed key custody, browser-encrypted preserve ingest, explicit chooser-driven preserve flows from ProsperMail and ProsperProductivity, shared safe memberships, version timelines, and dedicated alpha storage plus hosted API wiring while public preserve remains intentionally gated.
building
Prosper Events
Event publishing, discovery, organizer workflows, attendance, and ticketing
A standalone event-publishing and discovery product line now mounted as its own implementation repo, with public and organizer web/API scaffolds, alpha D1/R2 storage, seeded discovery, attendance intent, ticket categories, alpha checkout, capacity/waitlist handling, QR-ticket issuance, official icon assets, and custom map markers. Calendar, ProsperOrg, and DT integrations remain optional seams rather than the product home.
building
Prosper Calendar
Scheduling and event coordination
The current calendar surface lives inside Prosper Productivity, with calendar and event storage, reminders, attendees, hosted invite links, RSVP-by-token behavior, ICS downloads, and first conference-link groundwork toward broader coordination flows.
building
Prosper CloudFiles
Cloud storage, sharing, and canonical file identity
The current files, folders, sharing, preview, permission, and share-link surface lives inside Prosper Productivity today, with the first Preserve-to-Safe handoff now appearing beside it. The broader CloudFiles line can separate further as that storage and custody boundary matures.
building
Prosper Content Sites
First-party publishing, site operations, and governed content releases
A shared internal publishing platform for first-party Prosper properties, with a ProsperAuth-gated WYSIWYG editor, host-aware editor domains, a root content API, shared content DTO contracts, reusable collection data, preview/publish releases, and the first CMS-backed alpha ProsperApps runtime now live.
building
Prosper Creative Suite
Creative production and studio collaboration
A mounted product line centered on Creative Hub and PhotoLab, with active work across auth-required hosted use, root-owned creative API seams, team access, persisted documents, ORA import/export flows, and broader creative-cloud studio tooling.
building
Prosper Meet
Meetings and small-room communication
A first narrow meeting slice with a root-owned web app, productivity-backed room metadata and join bootstrap, a dedicated realtime worker, room-scoped persistent chat, host-admit guest flows, and room-stage polish while active participant counts stay intentionally small.
building
Prosper Productivity Suite
Knowledge work and collaboration
A mounted product line with a live preview web app, auth-bound workspace and file APIs, isolated drive roots, direct sharing, invite lifecycle, shareable file routes, visible permission indicators, richer signed-preview browser flows, the first explicit Preserve-to-Safe handoff, and the first shared calendar and meeting seams landing behind the productivity backbone.
building
ProsperAuth
Authentication and delegated access
Shared sign-in, session, passkey, recovery-email and recovery-phone controls, provider-aware hosted verification, bootstrap-portal, delegated-access infrastructure, approved-alpha developer intake, and public PKCE browser-client self-service for ProsperApps products.
building
ProsperCLI
Operator workflows and governed infrastructure access
A non-public operator command-line client for ProsperAuth and ProsperVault, with PKCE browser login, explicit account decision, OS-keychain refresh-token storage, and the first governed read-only vault commands for shared operational work.
building
ProsperID
Identity and trust controls
An optional browser-facing identity surface for trust, shared recovery methods, account continuity, secondary-email management, approved-alpha developer applications, and first-party Prosper subject identifiers without becoming a forced prerequisite for end users.
building
ProsperMail
Mail delivery and portable communication infrastructure
A root-owned mail governance, delivery, and mailbox seam now used by identity, productivity, creative, ProsperOrg, and company-site flows, with sender and template controls, Mailgun alpha callbacks, `prosperid.net` recovery and security mail branding, owner-scoped mailbox preview, and the broader privacy-first mail product and protocol direction still ahead.
building
ProsperOrg
Organization operations, hosted spaces, and commercial multi-tenant infrastructure
A mounted product line for a broader commercial organization platform, with hosted ProsperAuth access now wired, ProsperMail invite governance in place, and canonical planning living in its own repo so tenant, hosted-email, shared-drive, billing, and white-label needs do not collapse back into ChoirPower-only assumptions.
building
ProsperVault
Secret custody, recovery, and controlled machine access
A root-owned custody and recovery service seam with shared scopes, encrypted secret storage, machine-access keys, browser console access, Safe key-custody transit routes, first-party browser transit for preserve clients, and hosted secret-hydration support for rollout tooling.
building
Planned next lines
Where the portfolio can expand next beyond the current product and service backbone.
These tracks are not disconnected ideas. They are the next portfolio lanes being framed on top of the identity, mail, storage, and collaboration seams already taking shape in the shared platform.
Prosper CloudCalc
Spreadsheets, analysis, and structured calculation
A spreadsheet and calculation line planned as part of the broader productivity environment rather than as an isolated document silo.
planned
Prosper CloudWrite
Collaborative writing and documents
A writing and document line planned on top of the Prosper productivity backbone, intended to support clean collaboration without proprietary lock-in.
planned
Prosper Presentation
Presentations and visual communication
A presentation line planned to share storage, collaboration, and portability assumptions with the wider Prosper productivity suite.
planned
Prosper Whiteboard
Visual collaboration and shared thinking
A collaborative whiteboard line intended to bridge productivity and creative workflows without trapping users in a proprietary board format.
planned
Build with us
Selective bespoke SaaS work for third parties.
Bespoke SaaS for third parties
Partner organizations that want aligned software
We can develop and maintain SaaS on demand for third parties, but only when the resulting system can honestly comply with the Prosper Foundation Declaration.
service
Commercial filter
Not every project is a fit
A third-party SaaS engagement only makes sense for ProsperApps if the end result can genuinely comply with the declaration commitments.
Conversation