Book a demo

Camp · the front door for Camp Manager and Camp Photos · early access

One family for summer camp: operations and picture day, in one place to start from.

Camp is the front door for two built products on the same platform: Camp Manager runs the season -- registration, rosters, the Minor Consent Graph, and day-of check-in -- and Camp Photos runs the picture day and the parent store. The Minor Consent Graph is engine-enforced, not an export-and-hope checkbox: it governs what a form, a roster row, or a photo may do at the moment someone tries to use it, not just at the moment a parent signed a form. Each is built and live on its own host today. This page introduces the family, links you to the right one, and names honestly what is still a roadmap idea: one connected camp account tying registration and photo day together.

Book a conversation See the two built products →

There is no live registration form and no live checkout on this page. Camp Manager and Camp Photos each describe their own honest-off money posture on their own sites; this page repeats nothing beyond what those pages already say.

The family

Two built products, and one early-access idea

Camp Manager and Camp Photos are separate, production engines on separate hosts. Each card below is labelled honestly: what is built and live on that engine, and what -- on that same engine -- is still honest-off, per that engine's own docblock.

Camp Manager -- the operations engine

Camp Manager runs the season: session setup, the registration and roster data layer, day-of check-in with authorised-pickup enforcement, staff roles, and the Minor Consent Graph -- a machine-readable, revocable consent record that governs forms, rosters, pickup, medical visibility, communications, and photography for every camper. Check-in, pickup enforcement, attendance, staff roles, and the Minor Consent Graph are built and production-ready on campmanager.software. The live checkout interface that accepts a family's payment is honest-off there today, per its own docblock -- this summary does not claim more than that page already claims.

Built on campmanager.software · live checkout honest-off there

Camp Photos -- the picture-day store

Camp Photos runs one organized picture day -- portraits, cabin and activity groups, and candids -- captured against the camper roster, so every camper is accounted for. Afterward a parent opens a no-login store with a claim code and finds only their own camper, matched by a permission-checked roster lookup, never a face scan switched on without a parent's say-so. Consent-gated capture and the code-enforced cost floor are built and live on camp.photos. The branded parent store and the live checkout that takes a parent's payment are early access there, per its own docblock -- again, this summary does not claim more than that page already claims.

Built on camp.photos · branded store & live checkout early access there

One connected camp account -- early access

Today Camp Manager and Camp Photos are two separate, built engines on two separate hosts: a family registers with Camp Manager and separately claims a camper's photos on Camp Photos. The idea of ONE connected camp account -- a single registration that carries the same roster and the same consent record into the picture-day store, so a family signs up once -- is a roadmap concept. It is not built anywhere in the platform today. This page names that plainly rather than implying a hand-off that does not exist. There is no live registration form and no live checkout on this page; the only action here is booking a conversation.

Planned, not built · no live tie-in exists today

How it works

Using the Camp family today, five honest stages

There is no single sign-on across the family yet, so the path starts with picking the right surface and ends with a plain statement of what is not built.

Step 1 -- pick the surface for what you need

There is no single sign-on across the family today, so start on the surface that matches the job. Running the season -- sessions, rosters, consent, check-in, billing -- starts on campmanager.software. Running one picture day and the parent store starts on camp.photos.

Step 2 -- operations run on Camp Manager

A camp sets up sessions, collects the Minor Consent Graph record for each camper once, and runs day-of check-in with authorised-pickup enforcement -- all built and production-ready on campmanager.software. The live checkout that accepts a family's payment is honest-off there today. Those registration, roster, and billing endpoints are Camp Manager's own: camp.software does not assemble, proxy, or duplicate any registration, roster, or billing endpoint of its own, so a family's real first stop for what is live today is campmanager.software itself.

Step 3 -- picture day runs on Camp Photos

A camp runs one organized photo day against its camper roster, and afterward a parent claims only their own camper with a claim code -- consent-gated capture and the code-enforced cost floor are built and live on camp.photos. The branded parent store and live checkout are early access there.

Step 4 -- the connected account is not built yet

Carrying one registration, one roster, and one consent record automatically from Camp Manager into Camp Photos is a roadmap idea, not a shipped feature. Today a camp sets each surface up on its own. We name that gap plainly rather than describing a hand-off that does not exist.

Step 5 -- get in touch

Book a conversation and we will walk through both surfaces honestly: what is built and production-ready today, what is honest-off, and how the connected-account idea fits a camp's season. No card is charged, and nothing you send here is a registration for any camper.

Consent & privacy -- the honest version, repeated faithfully

What the family does with a camper's data, restated plainly

Camp Manager's Minor Consent Graph is the spine of the operations side: a machine-readable, revocable consent record per camper that governs forms, rosters, pickup, medical visibility, communications, and photography from one source of truth. Camp Photos matches a parent to their own camper by a permission-checked roster lookup, never a face scan switched on without a parent's say-so, and a camper's photo becomes sellable only when a released consent allows it. Underneath that posture, access is role-scoped and fail-closed: a staff member on shift reaches only what their assigned role is granted, directory listings can be suppressed, and no raw camper PII is surfaced beyond the role-scoped staff who genuinely need it -- privacy carried by how access is structured, not by a policy asterisk.

Facial recognition is a capability we are building and is not turned on today by design, not by omission -- the deliberate, safer choice for a roster made up of minors, not a convenience feature we simply have not gotten to yet. Face matching is a capability we are building and is not turned on today — the recognizer is not yet wired: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead. This page does not itself hold a camper record, a roster, or a photo -- it restates the same posture the two built engines already document on their own sites, and never claims more than they do.

What is built and what is early access -- plainly

Two engines are built and live. The connected account is not.

Built and production-ready today, each on its own host: Camp Manager's session setup, registration/roster data layer, day-of check-in and authorised-pickup enforcement, staff roles, and Minor Consent Graph; and Camp Photos' consent-gated, roster-matched picture day and its code-enforced cost floor. Live checkout is honest-off on both of those pages, exactly as their own docblocks state -- this page does not upgrade that claim.

Early access, and not built anywhere in the platform: one connected camp account carrying a single registration, roster, and consent record across Camp Manager and Camp Photos. There is no live registration form and no live checkout on camp.software itself -- the only action here is booking a conversation. This page carries no invented camp counts, no adoption numbers, and no named customers.

Book a conversation Read the FAQ →

FAQ

Common questions

Is Camp a separate company from Camp Manager, Camp Photos, or Homeroom?

No. Camp is the family name for two sibling products on the same platform, operated by the same team: Camp Manager (operations, at campmanager.software) and Camp Photos (the picture-day store, at camp.photos). camp.software is the front door that introduces both -- never a separate or independent company.

What is camp.software, exactly -- is it a third product?

No. camp.software is a directory and early-access front door, not a third engine. It summarizes the two built siblings and links to each. The only new idea it introduces is the roadmap concept of one connected camp account, and that idea is explicitly not built anywhere today.

Can I register my camper on this page?

No. There is no live registration form on camp.software. Registration happens on campmanager.software, and ordering camp photos happens on camp.photos -- and even on those pages, live payment checkout is honest-off per their own descriptions. The only action on this page is booking a conversation.

Is there one account across Camp Manager and Camp Photos today?

No. The two are separate, built engines on separate hosts today. A single connected account that carries one registration, roster, and consent record across both is a roadmap idea -- planned, not built. This page names that plainly rather than implying a live hand-off exists.

What happens to a camper's photo across the family?

On Camp Manager and Camp Photos, a camper's photo is never sold without permission, and a photo becomes sellable only when a released consent record allows it. Facial recognition is a capability we are building and is not turned on today; the default match is a permission-checked roster lookup, not a face scan. This page repeats that posture faithfully; it does not itself store or display any camper photo or record.

Does camp.software collect any camper or family data?

No. This page is display-only: no login, no roster, no consent record, and no photo is processed here. The only data path on this page is an email address if you choose to reach out, and that is not a registration for any camper.

How is camp.photos different from summercamp.photos?

camp.photos is one organized photo day plus the parent store -- a single pass that captures the whole camp against the roster. summercamp.photos is the whole-session shape: capture spread across the weeks of camp instead of one day. Same privacy-first pipeline, a different shape of program; pick the one that matches how a camp runs its photography.

How do I get in touch about the Camp family?

Email [email protected] to book a conversation. We will walk through Camp Manager and Camp Photos honestly -- what is built and production-ready, what is honest-off, and how the connected-account roadmap idea fits a camp's season. No card is charged, and no camper data is collected by reaching out.

Related surfaces

The wider Camp family and the platform underneath

campmanager.software

Camp Manager -- the minor-consent-first operations engine: sessions, registration and roster data, day-of check-in and authorised pickup, staff roles, and the Minor Consent Graph. Live checkout is honest-off there.

camp.photos

Camp Photos -- one organized roster-matched picture day and a no-login parent store opened with a claim code. Consent-gated capture and the cost floor are built and live; the branded store and live checkout are early access there.

summercamp.photos

The whole-session sibling of Camp Photos: capture spread across the weeks of camp instead of one organized day. Same privacy-first pipeline, a different shape of program.

pictureday.software

The same consent-first picture-day pipeline, tuned to the school-year picture-day schedule rather than a summer camp season.

homeroom.software

The K-12 publishing platform underneath the whole family: yearbook, picture day, student records, and family communication.