What we build
Products + shared platforms
We operate end-user products and the platform seams beneath them so the portfolio stays coherent.
Foundation-aligned software company
Building serious SaaS without the usual extraction logic.
ProsperApps develops and operates products, shared platform surfaces, and selective bespoke systems for organizations that need software they can trust over time.
The aim is a stronger kind of software company: one where the mission, ownership model, and product decisions are supposed to reinforce each other instead of working against each other.
Company shape
Own products and shared platforms
We build end-user products and the shared seams beneath them so the portfolio improves as a system.
Commercial filter
Selective bespoke SaaS
We can build for third parties too, but only when the work fits the model and the mission.
Operating constraint
Built for long-horizon trust
Portability, privacy, and product quality are treated as operating constraints rather than optional polish.
Why ProsperApps exists
A company shape that tries to support better product behavior.
ProsperApps is being built around the idea that ownership, incentives, and product quality are not separate topics. If the business model rewards lock-in, pressure, or quality decline, the product eventually shows it.
Operating base
Norway
ProsperApps is being positioned with Norway-based company operations and team presence.
Operating model
Foundation-aligned
The company is being shaped to reinforce long-horizon quality, portability, and trust instead of extraction.
Who it is for
Teams and organizations
The focus is practical software for operations, identity, collaboration, creativity, and communication.
Current work
Products and platform lines already operating or actively under construction.
Some of the portfolio is already live. Other parts are shared foundations or near-term product lines that make the broader ProsperApps direction possible.
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
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
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
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
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
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
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
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 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 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 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 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 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
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
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
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
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
How we work
Focused on useful software, disciplined platform choices, and selective partnerships.
ProsperApps is not meant to become a generic agency, a pure investment wrapper, or a portfolio of unrelated experiments. The company only works if the products, platform, and commercial choices stay coherent.
Commercial discipline
Not every opportunity is worth taking.
ProsperApps is interested in long-horizon software and aligned partnerships, not whatever short-term engagement happens to be available.
Platform thinking
Shared foundations where it helps, product specificity where it matters.
SaaSpawn lets us reuse the right infrastructure across solutions without flattening everything into generic product sludge.
Products
We build software for real work, not abstract growth theatre.
The focus is practical: organization operations, identity, collaboration, creative work, communication, and other areas where dependable software matters.
Join our team
Help build useful software with stronger incentives behind it.
ProsperApps is for people who want to raise the quality bar, build systems that matter in the real world, and do serious company work without pretending that extraction is the only viable business model.