Web Surfing StudiosWeb Surfing Studios

Engineering & stack

Every change follows the same controlled path to production.

Most aspiring developers build isolated portfolio projects: one repo, no pipeline, no teammates, no incidents. WSS is structured like a software organization — branches, pull requests, quality gates, artifacts, approvals, and infrastructure-as-code, all coordinated through shared platform tooling.

30+
in-scope repositories
3
deploy environments
50+
active participants

You are not expected to know all of this before joining. Most members begin with application development and gradually encounter deployment, cloud infrastructure, observability, CI/CD, and architecture as they progress through the program.

The controlled change pipeline

Professionals will recognize this immediately. Members learn it by using it every week.

  1. 01

    Pull request

    You open a PR on a feature branch. CI builds and validates it, and the automated PR Reviewer posts a graded review.

    Gates: title format, description length, dev-environment testing acknowledgment, submodule version validation.

  2. 02

    Artifact

    A successful build publishes a versioned ZIP to the Deployment Portal, tagged with a CI correlation ID that links API and client jobs.

    Build targets: .NET Framework MVC, .NET 8 APIs, React clients with Vite.

  3. 03

    Release

    A human triggers the deploy to Dev, Stage, or Prod. The Portal runs the right engine and streams status, logs, and an audit trail.

    Engines: IIS Web Deploy, local IIS on-prem, AWS Lambda via the deployment executor.

  4. 04

    Infrastructure change

    Terraform plans run on PR and on main. An approved plan is applied by TerraformRunner on ECS Fargate — never from a laptop.

    Saved tfplan in S3, applied at a pinned commit SHA, with logs streamed back to the Portal.

The shared platform every application plugs into

Identity, secrets, logging, email, and AI access are solved once, centrally, and consumed by every app — which is exactly how a real engineering organization operates.

  • Git

    Source control

    Source control, pull requests, branch policies, and CI workflows.

  • Deployment Portal

    Release orchestration

    Artifacts, environment releases, approvals, logs, and deployment execution.

  • WSS Identity

    Single sign-on

    Central SSO and role-based access.

  • Secrets Manager

    Configuration security

    Centralized project configuration and secrets.

  • Feature Flags

    Release tooling

    Centralized feature flag management with per-environment values, runtime resolution, and audit logging.

  • WSS Relic

    Observability

    Centralized logging and observability.

  • Terraform / WSSInfra

    Infrastructure-as-code

    Infrastructure-as-code with reviewed plans and controlled applies.

  • AI Portal / PR Reviewer

    AI governance

    Governed AI access and automated pull-request feedback.

AWS footprint

WSS runs a shared AWS environment supporting relational databases, serverless workloads, queues, object storage, email, containerized jobs, AI services, DNS, encryption, and controlled member access. Infrastructure is managed through Terraform.

How your responsibilities grow

Start with application development

Build features, fix bugs, work with databases, open pull requests, and deploy to development environments.

Move into production systems

Debug through centralized logs, work with shared platform services, and contribute across multiple applications.

Grow into advanced engineering

Take on cloud infrastructure, Terraform, CI/CD, distributed services, automation, and architecture-level work.

Technology stack

WSS maintains modern .NET 8 and React applications alongside established .NET Framework systems and AWS serverless workloads — all in active use.

Members maintain established MVC products while also shipping modern .NET 8 APIs and React clients.

Backend

  • C#
  • .NET 8 / ASP.NET Core
  • .NET Framework MVC
  • EF Core / EF6
  • REST APIs
  • gRPC where applicable

Frontend

  • React
  • TypeScript
  • Vite
  • Tailwind / Bootstrap

Cloud

  • AWS Lambda
  • S3
  • SQS
  • RDS
  • ECS Fargate
  • SES
  • Bedrock

DevOps

  • Git
  • CI workflows
  • Terraform
  • Docker
  • IIS
  • Deployment Portal

Data

  • MySQL
  • DbUp
  • Entity Framework

Members are not expected to use every technology. The stack you encounter depends on your phase, project, and interests.

Explore 30+ applications, tools, and infrastructure projects

Runtime & data

Scale-out and scheduled work — email delivery, log ingestion, AI requests, and scheduled automations — runs on AWS Lambda through the same Deployment Portal pipeline. A shared MySQL database backs every application, with EF Core and EF6 as the primary ORMs and DbUp-managed migrations. Authentication uses centralized SSO and role-based access for internal tools, with separate patterns for public applications.

Want this on your resume?

Members leave able to explain a real pipeline, a real cloud footprint, and the reasoning behind both.

Apply to Web Surfing Studios