Emailing Software · the email product home for schools and studios
A professional mailbox address your school or studio actually controls — not a vendor’s shared pool.
Most schools and studios send email from a generic consumer address or from a shared vendor domain. Emailing Software is the estate that changes that: branded mailbox addresses on domains your school or studio owns the identity on — pholio.email, educator.email, schoolnews.email, yearbook.email, and the rest of the owned .email fleet. The mailbox core — 50 pure mailbox engines — has landed. The MTA outbound brick is in flight; live sending is honest-off and we say so plainly rather than presenting early work as finished.
The mailbox core and the branded .email fleet are the built product. The MTA outbound sending brick is in flight; sending is honest-off until it is ready. This page is the email estate home — for physical print-and-mail, see mailing.software.
What emailing.software is — and what it is not
Emailing Software is the electronic email product home: mailboxes, branded addresses, and the sending infrastructure behind them. It is the estate that owns the mailbox core and the .email brand fleet, and it is the surface where a school administrator or studio owner learns what those products are and how to get them for their organization.
It is not mailing.software, which is the physical print-and-mail product: the pipeline that takes a recipient list and produces addressed physical mail pieces. The two products exist alongside each other because schools need both. They are siblings that serve different needs, share no infrastructure, and are never confused with each other on their own pages. If you arrived here looking for physical mail, the link above is the right door.
It is also not the product page for any single .email brand. When a school signs up for a branded mailbox on pholio.email, the product page they browse is pholio.email. When an educator wants a mailbox on educator.email, the product page is educator.email. Emailing Software is the estate home — the place that describes the whole catalog of branded mailbox addresses a school or studio can run from, not the individual sale of one of them.
Five things a legacy inbox or a generic parent-comms tool does not do
Four of these five are shipped, running capabilities in the platform the mailbox estate is built on today — not a roadmap. The fifth, guardian-language rendering below, is split on purpose: the static English/Spanish catalog it uses is shipped and running; per-guardian dynamic translation of message text is named as the honest-off, in-flight seam it actually is, not claimed as live. Each capability is the kind of thing that only exists because the mailbox layer and the school record layer share the same substrate, instead of a mailbox provider bolted on beside a separate contacts export.
1. The audience is computed live, not exported once
A message sent to “the yearbook committee” or “3rd grade families” is resolved against the actual roster, class, and team membership at the moment it sends — not a CSV someone exported in September and never touched again. A student who transfers out of the class stops receiving that class's mail the same day the roster changes, automatically, with no separate list to remember to edit.
2. Mail to a student record reaches the guardians actually on file
A message tied to a student record is routed to the guardians of record for that student — the same record the school already maintains for enrollment and emergency contact, not a second, hand-kept parent-email spreadsheet that quietly drifts out of sync with custody changes, new guardians, or a family that updated their contact info in one place but not the other.
3. Consent is gated per purpose and per channel
A family that consented to email communication has consented to email communication — nothing more. Each channel (email, text, voice) rides its own consent purpose, so an email opt-in never silently doubles as a text or robocall opt-in. This is enforced in code, not just in policy text on a settings page.
4. Guardian-language rendering: a real catalog today, per-guardian translation in flight
Message chrome renders in a guardian's saved language today when that language is English or Spanish (es-US), drawn from the same static catalog the rest of the platform uses — not a one-size-fits-all English template. Translating the free-text body of an individual message into a guardian's own language, on demand, is a separate, honest-off seam: it runs only through an in-VPC engine a school provisions, so message text (which is family PII) never leaves the VPC for an outside translation API, and it returns unconfigured rather than faking a result until that engine is provisioned. This item is in flight, not shipped-and-running.
5. Every address is traceable, and nothing vanishes silently
Addresses in the .email fleet support tagged, per-relationship sub-addresses, so a school or family can hand out a distinct address to each vendor or contact and know exactly which relationship a leaked or resold address came from. Mail to an address that does not exist bounces back to the sender rather than disappearing into a silent blackhole or a spam-farmed catch-all — fail closed, fail loud, never quiet data loss.
The mailbox core: what is built and what is in flight
The mailbox core is not a feature list. It is the infrastructure layer that makes the branded .email fleet real. Here is the honest status of each component.
The mailbox core — 50 pure engines landed
The mailbox core is the underlying layer that backs the branded .email fleet: 50 pure mailbox engines, meaning the protocol stack that handles message storage, retrieval, folder structure, and per-mailbox isolation at the infrastructure level. This is not a wrapper over a commodity provider; it is the actual mailbox layer the branded addresses run on. The core has landed — it is built, it is running, and it is what the .email fleet sits on top of. Built — landed
Per-brand mailbox isolation
Each .email brand runs in its own isolated segment of the mailbox core. A mailbox provisioned on pholio.email does not share an environment with a mailbox on educator.email or yearbook.email. The isolation is at the infrastructure level: the authentication flow, the storage namespace, and the delivery path are all brand-scoped. A compromise or misconfiguration on one brand does not propagate to another. Built
Deliverability posture — DNS scaffolding in place
The deliverability posture that backs the fleet covers the DNS record model every sending domain needs to land in an inbox rather than a spam folder: SPF records that authorize the sending infrastructure, DKIM signing keys that authenticate messages as genuine, and DMARC policies that tell receiving servers what to do with messages that do not pass. The scaffolding for these records is built into the .email brand fleet. When the MTA outbound brick connects, the DNS posture is already in place to support it. DNS scaffolding built
MTA outbound sending brick — in flight
The MTA outbound brick is the component that carries a message from a mailbox out to the recipient's mail server. This is the layer that powers live outbound email: a teacher at educator.email types a message and sends it; the MTA delivers it. This brick is in active development. It is not yet connected. No outbound message currently leaves the system through this path, and we say so rather than describing it as available. The deliverability DNS posture is already in place for when the brick connects. In flight — honest-off
The branded .email fleet
Each domain in the owned .email fleet is a real brand. 19 .email domains below are open to claim today — a live product page you can browse right now. A further 21 domains are owned by the estate but not yet claimable: their mail transport (MTA and DKIM) is not provisioned yet, so no claim page exists on them today, and we say so rather than showing a page that cannot actually receive mail. Mailbox activation is a founder-confirmed step; checkout is not open today and we say so on each product page.
Open to claim today
School Photo Mailboxes
schoolphotos.email
On-brand mailboxes for a school-photography business Open to claim today
Picture-Day Mailboxes
photos.email
The picture-day mailbox a school photo program runs on Open to claim today
School News Mailboxes
schoolnews.email
Mailboxes for a school's news and family newsletters Open to claim today
Preschool Mailboxes
preschool.email
A front-office mailbox for a preschool or early-learning center Open to claim today
Private School Mailboxes
privateschool.email
A branded mailbox for an independent or private school office Open to claim today
Charter School Mailboxes
charterschool.email
A branded mailbox for a charter school office Open to claim today
Backdrop Mailboxes
backdrop.email
A branded mailbox for your backdrop and scenic supply shop Open to claim today
Alphanumeric Mailboxes
alphanumeric.email
A clean letters-and-numbers mailbox that is yours to keep Open to claim today
Castra Secure Mailboxes
castra.email
A security-first mailbox for staff who handle sensitive records Open to claim today
Nunc Seasonal Mailboxes
nunc.email
An on-demand mailbox for a season or a single event Open to claim today
Voco Mailboxes
voco.email
A memorable address for the person everyone needs to reach Open to claim today
Campus Mailboxes
campus.email
Branded webmail for a high school or district office Open to claim today
Owned — address coming
Sealed Mailboxes
sealed.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Candor Mailboxes
candor.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Honesty Mailboxes
honesty.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Sincere Mailboxes
sincere.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Faithful Mailboxes
faithful.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Grounded Mailboxes
grounded.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Sturdy Mailboxes
sturdy.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Penned Mailboxes
penned.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Notecard Mailboxes
notecard.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Mailhaven Mailboxes
mailhaven.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Dearly Mailboxes
dearly.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Kinfolk Mailboxes
kinfolk.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Mailkeep Mailboxes
mailkeep.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Keepbox Mailboxes
keepbox.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Sendbox Mailboxes
sendbox.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Carry Mailboxes
carry.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Convey Mailboxes
convey.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Coast Mailboxes
coast.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Mainline Mailboxes
mainline.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Pier Mailboxes
pier.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Question Mailboxes
question.email
Owned by the estate; MTA and DKIM are not yet provisioned, so there is no claim page on this domain today. Owned — address coming
Pick your suffix
Type the part before the @ and choose one of the 19 .email domains that are open to claim today. This previews the address you would have — it does not reserve or activate a mailbox, and mailbox requests are not open yet.
Request this address
Mailbox requests are not open yet. This preview does not reserve or activate an address, and nothing is sent.
How the email estate fits the school platform
The branded .email fleet is one part of the Homeroom K-12 platform, which is the common substrate that runs yearbook, picture day, student records, family communications, and school management. Email is the communication layer that ties those products to the people who use them: a teacher at educator.email sends a message about a yearbook deadline; a yearbook adviser at yearbook.email sends proofs to a printing partner; a studio at pholio.email sends picture-day galleries to families.
The mailbox estate being inside the platform rather than a separate third-party service matters for two reasons. First, the addresses carry the right identity: a yearbook.email address signals yearbook, not a personal webmail account. Second, the mailbox system can eventually share the authentication layer and the contact infrastructure with the rest of the platform, so a guardian who has already consented through the platform can receive a message from the school at a verified address without a separate sign-in or a new opt-in loop. That integration path is planned; the mailbox estate being on the same substrate is what makes it possible.
The MTA outbound brick connects the mailbox layer to actual delivery. Until it is connected, the mailbox core holds messages and the estate’s DNS posture is in place, but no message leaves the system through this path. When the brick connects, the deliverability infrastructure — the SPF, DKIM, and DMARC setup already built for each .email brand — is what gives messages a real chance of landing in an inbox rather than a filter. We describe this plainly because “a professional email address” is only as useful as its ability to actually reach someone.
Electronic email vs. physical mail — two distinct products
The email estate and the physical mail product are siblings on the same platform, serving different needs. Here is what each one does and which page covers it.
Emailing Software — this page
Electronic email: mailboxes, branded addresses, and the outbound sending infrastructure behind them. A school or studio gets a professional address at a domain their program identity matches — yearbook.email, educator.email, pholio.email, and the rest of the .email fleet. The mailbox core is built; the MTA outbound brick is in flight; live sending is honest-off. Mailbox core built
Mailing Software
Physical print-and-mail: the pipeline that takes a recipient list, formats a physical mail piece, and delivers it through postal channels. This is the product for schools that send paper notices, fundraising letters, or physical yearbook order forms by post. Physical mail is a completely separate infrastructure from the email mailbox estate and lives at mailing.software. Physical mail — see mailing.software
What a school or studio gets from the email estate
A school that provisions a branded mailbox on one of the .email fleet domains gets an address that signals who they are, not just where mail can be routed. The yearbook program’s adviser does not receive messages at a first-initial-last-name address at the district’s domain, which changes when the adviser changes. They have [email protected], or [email protected], or a form of the school’s name at the right domain — an address whose identity travels with the program rather than with the individual account holder.
A studio provisioned on pholio.email has the same stability: the studio’s gallery delivery, its client correspondence, and its booking confirmations go from a pholio.email address that identifies the studio as a photography business rather than a personal webmail account. When picture-day families receive a message from a pholio.email address, the domain itself communicates what the email is about.
The deliverability posture matters because a professional address that reliably lands in spam is not a professional address. The DNS scaffolding that backs the .email fleet — the SPF authorization records, the DKIM signing setup, the DMARC policy — is built for each brand in the fleet. When the MTA outbound brick connects and live sending is active, the infrastructure is already in place to support inbox delivery. We describe this as what it is: planned, in place, and waiting on the outbound brick to be ready.
The mailbox activation step is a founder-confirmed step that is currently off. A school or studio that wants to reserve a branded address or get into the early-access queue can get in touch through the contact link below.
Pricing — planned tiers, no free plan
There is no free tier here, on purpose. A mailbox that costs nothing to the person using it is usually being paid for another way — ads, or a data-resale relationship with the provider. The email estate is built the other way: paid means the mailbox is run for whoever is paying for it, full stop. The four tiers below are the planned shape of that: an individual mailbox, a family plan, a per-seat school-staff plan, and a per-student roster plan for whole-school rollout. No card is charged today, and checkout is not open yet — this is a preview of the tiers being built, not a live purchase.
Individual
$4/mo per person
Planned — coming soon
Planned for one educator, adviser, or studio owner who wants one branded mailbox address and nothing shared.
- One mailbox on a brand of the .email fleet (yearbook.email, educator.email, pholio.email, and the rest)
- The deliverability posture (SPF, DKIM, DMARC) already built for the brand
- No ads, no data resale -- the mailbox is run for the person paying for it
Family
$9/mo per household
Planned — coming soon
Planned for one household with more than one person needing a mailbox -- one account holder, shared billing.
- Everything in Individual
- Multiple mailboxes under one household account holder
- Guardian-of-record routing when tied into a school's platform account
School Staff
$3/user/mo per staff seat
Planned — coming soon
Planned for a school or studio provisioning mailboxes for its staff -- teachers, advisers, coordinators -- seat by seat.
- Everything in Individual, provisioned per staff member
- Roster-sync audience resolution for staff distribution lists
- Per-purpose consent gating carried over from the platform's family-communication settings
Roster
$1/student/yr per student, per school year
Planned — coming soon
Planned for a whole-school rollout: guardian-of-record mail routing for the full student roster, priced per student per year, not per mailbox.
- Guardian-of-record routing (resolveRecordNotifyRecipients) for the full roster
- Language-aware delivery: message chrome renders in each guardian's saved language (en / es-US catalog today)
- Consent-gated by purpose, enforced per channel, for the whole school
Prices shown are the planned rates for when sign-up opens. Nothing on this page collects a card, and no plan here can be purchased today.
What is in flight and what is planned
These are not presented as available today. They are named so a school or studio choosing this platform can see where the email estate is going and what the honest build trajectory looks like.
MTA outbound sending — connect the brick
The outbound MTA is the component that carries a message from the mailbox to the recipient’s mail server. The brick is in active development. When it connects, the DNS posture already built for each .email brand is in place to support delivery. This is the most significant in-flight piece; when it is ready, the estate moves from a mailbox system that receives and stores messages to one that sends them. In flight
Mailbox activation and provisioning flow
The activation step that provisions a specific mailbox on the .email fleet is a founder-confirmed step, currently off. The catalog and the product pages exist; the live checkout and the automated provisioning flow are planned to open when the outbound brick is ready. A school or studio that wants to be in the early-access queue can get in touch. Planned — early access queue open
Platform authentication integration
The path where a guardian or school contact who has already logged into the Homeroom platform can receive and reply to email from a .email brand address without a separate login is a planned integration. The shared authentication substrate that makes this possible is part of the broader platform; the email-side integration with it is a subsequent step after the outbound brick connects. Planned
Inbound delivery surface
The full inbound delivery surface — where a message sent to a .email address is fetched, presented in a web interface, and available to the mailbox holder — is part of the built mailbox core. The interface that a school staff member uses to read their email at yearbook.email is a surface being built on top of the core. The storage and protocol layer is built; the front-end reading surface is in active development. In progress
Common questions
What does “the mailbox core has landed” mean?
It means the infrastructure layer that backs the .email fleet — the 50 pure mailbox engines that handle message storage, retrieval, folder structure, and per-mailbox isolation — has been built and is running. “Landed” is the honest status for work that is complete and in production, as distinct from work that is in flight or planned. The mailbox core is the foundation; the MTA outbound brick and the inbound-reading surface are what is being built on top of it.
Why is live outbound sending honest-off?
The MTA outbound brick is the component that carries a message from the mailbox to the recipient’s mail server. It is in active development and is not yet connected. Until it is, no outbound message leaves the system through this path. We describe this as honest-off rather than burying it because “a professional email address that cannot send email yet” is important information for a school considering whether to sign up now or wait until sending is live.
What is the difference between emailing.software and mailing.software?
emailing.software is this site: the electronic email product home, covering mailboxes, branded .email addresses, and the outbound sending infrastructure. mailing.software is the physical print-and-mail product: the pipeline for sending addressed paper mail pieces through postal channels. The two products are siblings on the same platform but serve entirely different needs and share no infrastructure. If you are looking for the physical mail product, the link is in the navigation and in the body of this page.
Can a school get an address at multiple .email domains?
Yes. A school that runs a yearbook program, a photography studio, and a student newspaper could have addresses at yearbook.email for the yearbook program, pholio.email for the studio, and schoolnews.email for the newspaper — each scoped to its program identity, each isolated at the mailbox-core level. The activation step for each brand is separate; a school is not required to activate all of them at once. Mailbox activation is currently a founder-confirmed step; early-access details are available through the contact link.
Is the email estate separate from the school’s existing email system?
Yes. A mailbox at yearbook.email or educator.email is a professional address a school or studio adds, not a replacement for the district’s existing email domain. The typical use case is a program-specific address — the yearbook program, the photography studio, the student paper — that carries the program’s identity rather than routing through the school district’s general IT domain. The two email systems coexist; a teacher can have both a district address and a yearbook.email address for the parts of their work that belong to the yearbook program.
What does the deliverability posture actually cover?
The DNS record model built for each .email brand covers three layers. SPF (Sender Policy Framework) records authorize the sending infrastructure as permitted to send from the domain, so receiving servers know the message is not a forgery. DKIM (DomainKeys Identified Mail) signing keys authenticate each message cryptographically, allowing receiving servers to verify the message has not been altered in transit. DMARC (Domain-based Message Authentication, Reporting, and Conformance) policies tell receiving servers what to do — quarantine or reject — if a message fails the SPF or DKIM check. These three records together are what give a professional email address a real chance of landing in an inbox rather than a spam filter. The scaffolding for all three is built into the .email fleet.
How do I get a branded email address for my school or studio?
Mailbox activation is currently a founder-confirmed step; automated self-service checkout is not yet open. Schools and studios that want to reserve an address or get into the early-access queue can get in touch through the contact link on this page. The product pages for individual .email brands (pholio.email, educator.email, yearbook.email, and the others) also have contact paths. There is no pricing commitment and no signup that bills.
Is student data handled through the email system?
The mailbox estate is a professional communications tool for school staff, studio operators, and program coordinators — not a channel for student data. A teacher at educator.email has a professional address for their own correspondence. The broader platform has its own consent and privacy architecture for handling student data; the email estate is the professional address layer for the adults who use it, not a student data system.
Related properties
Mailing Software
The physical print-and-mail sibling: the pipeline for schools and studios that need to send addressed paper mail pieces by post. Electronic email and physical mail are two distinct products on the same platform.
Pholio Email
The Pholio branded mailbox: a professional address at pholio.email for school photography studios and picture-day coordinators. One of the .email fleet domains built on the mailbox core.
Educator Email
A professional mailbox for educators, advisers, and school staff. An address at educator.email carries a teaching identity that travels with the person, not the district.
Yearbook Email
A branded mailbox for the yearbook program: adviser, editor, and distribution team. An address whose identity belongs to the yearbook, not the school district’s general IT domain.
Homeroom
The K-12 platform the email estate is part of: yearbook, picture day, student records, family communications, and school management on one shared substrate. The email estate is the communication layer inside that platform.
What is built and what is honest-off
The mailbox core — 50 pure mailbox engines — is built and running. The branded .email fleet (pholio.email, educator.email, schoolnews.email, yearbook.email, photos.email, preschool.email, privateschool.email, charterschool.email) has product pages built and the brand estate in place. The deliverability DNS scaffolding (SPF, DKIM, DMARC) is built for each .email brand. The MTA outbound brick — the component that carries messages to recipients — is in flight and honest-off; live sending is not claimed as available and we say so rather than describing in-progress work as finished. Mailbox activation and checkout are founder-confirmed, currently off. The inbound reading surface and the platform authentication integration are in progress and planned. If you want to reserve an address or discuss early access, the contact link is below.
Emailing Software is an email infrastructure product from Stanley Studios — the same family behind the Homeroom K-12 platform. This page covers the electronic email estate. For physical print-and-mail, see mailing.software.