Stanley StudiosBook a conversation

Stanley Studios · The software arm · A portfolio for schools and studios · Early access

The software portfolio for schools and studios.

Stanley Studios builds the software behind a portfolio of school and studio products — the publishing platform, the yearbook suite, picture-day commerce, the authoring tools, the program apps, and the identity and tuition rails. One platform sits underneath them all: shared records, consent, and server-side pricing. The engines are built; live payment is honest-off today. Book a conversation and we will show you the current state, honestly.

One platform underneathshared roster, consent, and commerce + payout rails behind every product
Charged = displayedacross the commerce products every price is resolved server-side; the buyer never names the number
Consent-gated by defaultstudent and family data is school-owned; minors’ data is never made public or sold
Early accessthe engines are built and production-ready; live payment is honest-off and founder-gated

How it fits together

A portfolio, not a pile of tools

The products interoperate because they share one platform underneath. Every step is described as it is built today.

Step 1 · One platform underneath every product

The portfolio is not a pile of separate tools. Underneath sits one platform — the roster, the records, the consent ledger, and the shared commerce and payout rails. A school sets its data up once; each product reads the same roster instead of asking a family to enroll again. This is why the products fit together rather than merely sit side by side.

Step 2 · Adopt one product or the whole suite

Each product is its own site and its own focused app. A school can adopt a single product — just the yearbook storefront, or just the photography order flow — or the whole suite. No product is a paywall in front of another, and adopting one does not require the rest. The suite is a set of real, separable products, not a bundle you must swallow whole.

Step 3 · Server-priced and consent-gated by construction

Across the commerce products the unit price is resolved server-side, so what a buyer sees is what bills — the amount is never typed in by the buyer. Student and family data is owned by the school and consent-gated: a family opts in before any contact is used, minors' data is never made public, and nothing is sold or shared with outside companies. Consent can be withdrawn at any time.

Step 4 · Early access — the engines are built, the money rails are honest-off

The engines across the portfolio are built and production-ready. The live payment and live checkout rails are honest-off: present in the platform, founder-gated, not enabled for live transactions. No product has a live paying customer yet. There is no signup funnel and no pricing commitment on this page. A conversation — a real look at the current state of a product — is the honest next step.

The portfolio

Six product families — every one a real, owned product

Each family is labelled honestly: Built means the underlying software is production-ready. Live money rails are honest-off across the whole portfolio today — the engines are built; live payment is founder-gated.

The publishing platform — the core every product sits on

The platform at homeroom.software is the system of record underneath the whole portfolio: the roster, the records, the consent ledger, and the shared commerce and payout rails. A school sets its data up once; every other product reads the same roster rather than asking for it again. Prices are resolved server-side and payouts split server-side as an exact sum, so the same rails serve every commerce product in the portfolio. The platform engine is built and production-ready. The live payment rail that moves money is honest-off — present in the platform, founder-gated, not yet enabled for live transactions. A conversation is the honest next step.

Built · live payment honest-off

The yearbook suite — production, storefront, sell-through, and giving

A complete yearbook program built as separate, focused products on one set of rails: yearbook.press is the full production program (design, photos, proof, print); yearbook.sale is the direct-sales storefront where a family reserves a book at a server-set price; yearbook.marketing is the sell-through reminder engine that reaches only the families who have not ordered; yearbook.fund is the sponsor-a-book giving surface; and yearbook.cloud is the digital edition and archive. The ordering, pricing-window, and payout engines are built and production-ready. Live checkout is honest-off across the suite.

Built · live checkout honest-off

School and event photography — picture-day commerce and the studio side

The photography products carry the picture-day and studio order flow: k12.photos is the picture-day commerce and studio surface; pictureday.software runs the picture-day itself; photographer.software is the working photographer's tool; and seniorphoto.network and homeschool.photos serve their own audiences. Each resolves the unit price server-side so what a family sees is what bills, splits every sale four ways (studio, photographer, school, platform) as an exact sum, and keeps galleries consent-gated. The order rails are built and production-ready; live checkout is honest-off.

Built · live checkout honest-off

Authoring tools — the structured editor for words and books

One structured-document editor substrate powers the authoring products: composition.software is the writing desk where a student drafts, revises with tracked revision colors, and publishes to the literary magazine or newspaper; playwright.software and playscript.software are the stage-play writing editor and the living promptbook; and theatre.software is the whole-school theatre-program platform. Adviser approval is fail-closed — student work cannot publish until the adviser gate clears. The editor substrate is built and production-ready; the publishing money rails are honest-off.

Built · early access

Program and activity software — one focused app per program

A family of focused operational apps, one per program, each its own owned product site: afterschool.software, campmanager.software, musicschool.software, danceschool.software, learningcenter.software, lunchroom.software, and mediacenter.software, among others. Each runs the day-to-day of its program on the shared roster, consent, and payout rails rather than a separate silo. The apps are built and production-ready; enrollment and payment money rails are honest-off across the family.

Built · early access · money honest-off

Identity, tuition, and the operational rails

The cross-cutting products every school touches: studentid.software issues student IDs from the same roster that runs everything else; tuition.software is the tuition and school-payments surface; and parent.software is the family front door across the products. These read the one shared record so a family is set up once, not once per product. The identity and records engines are built and production-ready; the tuition and payment money rails are honest-off, founder-gated, and not enabled for live transactions today.

Built · money honest-off

For schools, studios, partners, and developers

However you are evaluating the suite, the answer is honest

Schools and studios

Adopt one product or the whole suite — the yearbook storefront, the picture-day flow, a single program app, or the platform itself. No product is a paywall in front of another. The base platform and standing up a storefront are free where they apply; the commerce products take only a small per-sale fee at split time — and live payment is honest-off today, so nothing is charged yet. You are never signing up on this page; you are booking a conversation.

Partners

If you are weighing how a product fits your workflow or an integration, the honest step is to talk through the current state of the software: what is built, what is honest-off, and what an integration would actually involve. We do not advertise integrations that are not built. The conversation is with the people who wrote the code.

Developers

The architecture is the pitch: one platform of record underneath, server-side price resolution so what is shown is what bills, exact-sum payout splits, and a consent ledger that keeps minors’ data private by construction. Every product reads the same roster rather than duplicating it. The core platform lives at homeroom.software.

To book a conversation: [email protected].

What is built and what is honest-off — plainly

The engines are built. The money rails are not yet enabled.

Built and production-ready today: the core publishing platform (roster, records, consent ledger, shared commerce and payout rails); the yearbook suite (production, storefront, sell-through, sponsor-a-book giving, and the digital edition); the photography-commerce products (server-resolved pricing, four-way exact-sum payout, consent-gated galleries); the authoring tools (the structured editor for composition, playwriting, and the school theatre program, with fail-closed adviser approval); the program apps (one focused operational app per program on the shared rails); and the identity and records rails (student IDs and the family front door from the one shared roster).

Not yet enabled for live use: the payment rails — live checkout, tuition and enrollment payments, and any card charge. These are honest-off: present in the platform, founder-gated, not enabled for live transactions. There is no live checkout here. No billing. No subscription. No signup funnel. No product has a live paying customer yet. A conversation is the honest next step.

Where to go next

The platform, a product, or the full directory

homeroom.software is the core publishing platform — the foundation every other product sits on. yearbook.press is the complete yearbook program, and yearbook.sale is its direct-sales storefront. k12.photos is the picture-day commerce and studio side. composition.software is the writing and publishing desk. And stanleystudios.llc is the full house-of-brands directory — every owned site across every vertical, if you want to browse the whole family rather than the software portfolio.

Early access · Schools, studios, partners, and developers · See the current state honestly

Book a conversation

The portfolio is in active development. No product has a live paying customer yet. We do conversations that show the current state honestly: which engines are built, which money rails are honest-off, how one platform sits underneath the products, and what adopting a single product or the whole suite would actually look like. There is no pricing commitment and no signup. If it looks right for your school, studio, or partnership, we discuss what early access looks like.

To book: email [email protected].

FAQ

Common questions

What is Stanley Studios?

Stanley Studios is the software company that builds and ships the products in this portfolio. It is a for-profit company, not a school and not a nonprofit. This site is the software arm's front door: it presents the products the company engineers — the publishing platform, the yearbook suite, the photography-commerce products, the authoring tools, the program apps, and the identity and operational rails — for schools, studios, partners, and developers evaluating the suite.

How is this different from stanleystudios.llc?

stanleystudios.llc is the house-of-brands directory: a categorized index of every owned site across every vertical — the marketing front door to the whole domain family. stanleystudios.software is narrower and product-facing: it is the engineering portfolio, describing the software the company builds, what each product does, and what is built versus honest-off, for anyone evaluating the suite rather than browsing the full directory.

Are these products live? Can I buy or start today?

The engines across the portfolio are built and production-ready. The live payment and live checkout rails are honest-off — present in the platform, founder-gated, and not enabled for live transactions today. There is no live checkout, no billing, no subscription, and no signup funnel on this site. No product has a live paying customer yet. Early access is the honest posture, and a conversation is the honest next step: email [email protected].

How do the products fit together?

One platform sits underneath the whole portfolio — the roster, the records, the consent ledger, and the shared commerce and payout rails, at homeroom.software. A school sets its data up once and each product reads the same roster rather than asking a family to enroll again. That shared foundation is why the products interoperate instead of merely coexisting.

Do I have to adopt the whole suite?

No. Each product is its own site and its own focused app. A school can adopt a single product — just the yearbook storefront at yearbook.sale, or just the picture-day flow at k12.photos — or the whole suite. No product is a paywall in front of another, and adopting one never requires the rest.

Is the price a buyer sees the price they pay?

Yes, across the commerce products — by construction. The unit price is resolved server-side from the school's catalog at order time; the buyer's submitted amount is never trusted. The price shown is the price that bills, and every sale splits across its legs as an exact sum. Because the live payment rail is honest-off today, no card is charged — but the pricing is built to be honest the moment it is enabled.

How is student and family data handled?

Student and family data is owned by the school and is never sold to or shared with outside companies, advertisers, or third parties. Data involving minor students is consent-gated: a family opts in before any contact is used, and minors' data is never made public. Consent can be withdrawn at any time, and data can be exported. This posture is the same across every product in the portfolio — it is a property of the shared platform, not a per-product promise.

Does Stanley Studios do partner integrations or custom work?

We do conversations. If you are a studio, a district, or a partner weighing how a product fits your workflow, the honest next step is to talk through the current state of the software with us — what is built, what is honest-off, and what an integration would actually involve. We do not advertise integrations that are not built. Email [email protected].

What does it cost?

There is no pricing table on this page and no pricing commitment. The base publishing platform and the ability to stand up a storefront are free where they apply; the commerce products take only a small per-sale fee at split time, deducted when a sale actually happens — but live payment is honest-off today, so nothing is charged yet. Pricing for a specific product is a conversation, not a checkout.

How is this related to homeroom.software?

homeroom.software is the core publishing platform — one product in this portfolio, and the foundation the others sit on. Stanley Studios is the company that owns and ships it alongside the yearbook suite, the photography products, the authoring tools, the program apps, and the operational rails. If you want the platform itself, start at homeroom.software; if you want the whole product portfolio, you are already at the right place.