Our projects
Participants work across 30+ applications, tools, and infrastructure projects spanning internal platform systems, public-facing products, shared libraries, automation, and cloud infrastructure. The catalog includes live production applications, internal platform systems, shared infrastructure, and products in development.
You do not need to understand every WSS project. As you progress, you can contribute in areas that align with the skills you want to build.
Examples
MergeJam · Candidate Portal · FeatureFlags · LMS
Work may include React UI, APIs, forms, validation, database changes, and end-to-end features.
Examples
Deployment Portal · Email Service · PingMyApp · WSS Identity
Work may include API endpoints, service logic, integrations, queues, authentication, and database changes.
Examples
WSSInfra · TerraformRunner · Deployment Portal · WorkflowTemplates
Work may include Terraform, CI/CD, AWS services, deployment automation, and infrastructure workflows.
Examples
AI Portal · PR Reviewer · Help Bot · TipOfTheDay
Work may include AI integrations, prompt behavior, governance, automation, and supporting APIs.
Examples
WSS Relic · PingMyApp · Deployment Portal
Work may include logging, filtering, incident troubleshooting, monitoring, and reliability improvements.
Examples
Existing MVC applications · Older React applications · Shared platform libraries
Work may include migrating legacy patterns, improving architecture, updating UI technology, and reducing technical debt.
WSS-InternalApps
This is what separates WSS from a portfolio project. We built and operate our own release console, identity provider, secrets vault, log aggregator, and AI governance layer — and participants contribute to all of it.
Internal applications spanning release operations, developer experience, observability, and automation.
Release orchestration
The central release console for every WSS application and for infrastructure: artifact storage, environment management, deployment execution, and Terraform plan approval.
Participants work on: Pipeline configuration · Deployment engines
.NET 8 API + React SPA
Identity platform
The central authentication portal and identity directory used across most WSS internal applications, issuing JWTs and short-lived SSO redirect tokens.
Participants work on: Auth flows · User group management
.NET 8 API + React SPA
Configuration security
An internal vault for credentials, API keys, and sensitive configuration, distributed to WSS applications at deploy time instead of living in source.
Participants work on: Secret lifecycle workflows · Access control
.NET 8 API + React SPA
Release tooling
Centralized feature flag management across Dev, Stage, and Production, with project grouping and audit logging on every change.
Participants work on: Flag API · Admin UI
.NET 8 API + React SPA
What participants use to learn, apply, propose, and measure their work.
Learning platform
The onboarding and curriculum platform: structured modules, assignments, video lessons, assessments, and progress tracking for Phase 1 participants.
Participants work on: Curriculum features · Assignment workflows
.NET 8 API + React SPA
Delivery metrics
A developer contribution dashboard aggregating commit and pull request activity from Azure DevOps and Git.
Participants work on: API aggregation logic · Dashboard visualizations
.NET 8 API + React SPA
Proposal system
An internal feature proposal system: submit ideas, vote, comment, and receive admin feedback through a structured workflow.
Participants work on: Proposal lifecycle · Voting logic
.NET 8 API + React SPA
Slack Q&A service
A Slack-based question and answer tool built during a WSS hackathon: five independent services delivering fast answers to recurring program questions.
Participants work on: Lambda services · Slack integration
AWS Lambda
How we see what production is doing, and how the platform talks to people.
Centralized logging
A centralized log viewer for troubleshooting across every WSS application, ingesting logs over SQS from the shared platform logger.
Participants work on: Log search UX · Ingestion pipeline
.NET 8 API + React SPA
Distributed delivery pipeline
The distributed email pipeline for transactional and workflow messages: a REST API validates requests, SQS queues them, and dedicated sender Lambdas deliver through SES.
Participants work on: Queue processing · Lambda handlers
.NET 8 API + Lambda
QA tooling
An internal tool that intercepts and stores outbound email for developer and QA inspection, and never delivers to real inboxes outside production.
Participants work on: Email capture integration · Search and filter UI
.NET 8 API + React SPA
Scheduled automation
A scheduled Lambda that picks a random development tip, generates an explanation with Bedrock, and posts it to Slack every day.
Participants work on: Tip content curation · Bedrock prompt tuning
AWS Lambda
Governed AI access, and automation that reviews and supports the work.
AI governance
The gateway for AI API access across WSS: key issuance, usage tracking, cost monitoring, and admin governance.
Participants work on: Key lifecycle · Usage analytics UI
.NET 8 API + React SPA
Bedrock proxy
A serverless proxy between external API consumers and Amazon Nova models, enforcing authentication, model restrictions, and request logging.
Participants work on: Lambda handler logic · Auth layers
AWS Lambda
CI automation
Automated pull request review inside CI: it diffs branches, sends patches to Bedrock through the Aider CLI, and returns a structured JSON review.
Participants work on: Review instruction tuning · Grading criteria
Shared platform tooling
The public recruiting surface, also maintained by participants.
Public marketing site
The public site for Web Surfing Studios: program information, project highlights, history, FAQ, contact, and the path into the Candidate Portal.
Participants work on: Content updates · Page structure
React SPA (static)
Applicant tracking
The application intake system for prospective participants — one of the first parts of the platform an applicant sees.
Participants work on: Application workflows · Admin bulk operations
.NET 8 API + React SPA
WSS-ExternalApps
Products with public users and public-facing domains, built and maintained by participant teams on top of the platform above.
Uptime monitoring at scale, an AI project manager, nonprofit volunteer management, a community showcase, and an accessibility-first communication app.
Uptime monitoring platform
Website and API uptime monitoring. Users create subscriptions, add monitored endpoints, configure check intervals, and receive alerts the moment a service goes down or degrades.
Participants work on: MVC feature development · Lambda processing logic
MVC + Lambda
AI project manager
An AI project manager embedded in Slack and Microsoft Teams. It tracks workflows, checks in proactively, flags blockers, and keeps teams aligned without a human PM chasing status updates.
Participants work on: Web UI features · Slack bot logic
ASP.NET MVC
Volunteer management platform
Volunteer management for nonprofits and community groups: recruitment, event scheduling, participation tracking, and organization profiles.
Participants work on: Full-stack MVC features · Role-based permissions
ASP.NET MVC
Community showcase platform
A project showcase and community platform where participants post work, browse submissions, upvote, comment, and react — backed by real-time updates.
Participants work on: API endpoints · React UI
.NET 8 API + React SPA
Accessible communication platform
An accessible communication platform for people who struggle with complex devices: large buttons, readable text, calls, messages, photos, and reminders, with caregiver remote management.
Participants work on: Accessible UI patterns · Caregiver workflows
.NET 8 API + React SPA
WSS-Tools
Not standalone products — the engineering substrate everything else runs on. Participants reach these in Phase 2 and Phase 3.
Terraform configuration for all WSS AWS infrastructure: 14 workspaces, S3 remote state, and a plan-on-PR, approve-then-apply pipeline.
A .NET 8 Fargate worker that executes approved Terraform plans: it clones the infra repo at a pinned commit, downloads the saved plan, applies it, and streams logs back to the Deployment Portal.
A shared CI workflow library — no application code, only reusable workflow_call definitions consumed by every WSS repository.
The shared platform submodule for modern applications: DbUp migrations, SQS logging, JWT and auth configuration, AWS helpers, email templates, and middleware.
The legacy .NET Framework 4.8.1 shared submodule behind the MVC applications, kept backward compatible while those apps migrate.
Members join a project team after Phase 1 and own real work items from there.
