Skip to content

Is there a separate YC / marketing web app?

Short answer

No. WorkWingman does not ship a special single-page web app only for Y Combinator reviewers or only for marketing.

What people sometimes call “the YC SPA” is really other things that already exist:

  1. The public website (normal multi-page site).
  2. The same product app you use in the cloud, entered with a YC invitation code.
  3. Docs inside that product that only certain audiences can see.

Three things that are easy to mix up

What What it actually is Who it’s for
Public website Server-built multi-page site (marketing, team, contact, “open the app”) Anyone on the public web
Cloud product app The Angular product UI (same family as the desktop app), hosted in the browser Invited people (YC or team), after they sign in or redeem a code
Hosted docs Markdown docs filtered by “audience” after you’re in the cloud product People whose session audience is allowed for each doc

There is no fourth “YC-only SPA codebase” sitting beside those.

What YC reviewers use instead

Public site door

On the public site’s Open the app page, one door is labeled YC reviewer. It sends people to the cloud product host and tells them to enter an invitation code. That page is part of the multi-page marketing site, not a separate SPA project.

Cloud product with a YC invitation

YC access is an audience on the cloud product: redeeming the YC invitation creates a private workspace and a session labeled for YC reviewers. Team invitations use a different audience on the same product surface. Reviewers are not given a different app binary; they get the product under different access rules.

Docs marked for YC

Some documentation is listed in a cloud docs list (cloud-docs-manifest.json) with audiences such as yc-reviewer or team-test. After sign-in, the product only shows docs allowed for that session’s audience. That is access control on docs, not a separate website project named “YC SPA.”

What the public site is not

  • Not the desktop Angular app rebuilt for marketing.
  • Not a React/Vue “landing SPA” repo folder.
  • Not the place where invitation codes create private product workspaces (that happens on the app host).

The company deliberately keeps marketing as multi-page server pages and product as the Angular app. That split is intentional (see the MPA / public-site docs).

If someone asks “where’s the YC SPA?”

Safe reply:

There isn’t a separate YC SPA. YC reviewers use the cloud product with a YC invitation, and they may see a filtered docs set. Marketing lives on the multi-page public site, which only points them at the app.

Open checks

  • TODO(verify): whether ops still keep a separate frozen cloud service only for YC, or one app service with two invitation audiences (docs and configs have described both over time).
  • TODO(verify): exact live URLs on every environment if someone needs a click path beyond prod names in ops docs.