Book a demo

Compare

Pholio vs. the school-photography incumbents — honestly.

The established names in school photography are capable and well-run. We won’t disparage them, we won’t invent claims about them, and we won’t single out any one company by name. Instead we compare Pholio against the three incumbent models. Where we have not independently verified how an incumbent behaves, we say “Not verified” — the cells below are a starting point to confirm, not a finished claim. The edges we assert for Pholio are properties of our own architecture — things you can verify in a demo or in your own deployment, not promises you have to take on trust.

Pholio’s split percentages are marked early access until finalized; incumbent cells marked “Not verified” need confirmation before publish.

Jump to: The national portrait companies · The cloud school-photo platforms · The studio-storefront SaaS

The one axis you don’t have to take on trust

The incumbents are good at logistics, catalogs, and storefronts. Pholio’s difference is not a bigger promise about children’s photos — it is that the privacy posture is yours to inspect. Pholio is self-hosted, so the software, its storage, and its network egress sit in a VPC you control and your own people can audit. AI face-find — an early-access feature, off by default until a school configures it — runs against an encoder endpoint you set, so you decide where that processing happens and you can confirm it rather than believe it. Consent is enforced as a database constraint rather than a sales-flow step, so it is visible in the schema. Those are the edges we stand behind, and we state them as properties you can check; everything else below is a fair, verifiable contrast.

Pholio vs. the national portrait companies

Pholio vs. the national portrait companies -- incumbent cells marked 'Not verified' need confirmation before publish.
DimensionThe national portrait companiesPholio
Hosting / data locationA cloud-hosted vendor pipeline. Not verified -- to confirm before publish.Self-hosted: the deployment runs in a VPC you control, so where photos are stored — and what the service is allowed to reach — are yours to configure and audit.
AI face-find on minorsFace-matching offered; runs in the vendor cloud. Not verified -- to confirm before publish.AI face-find and match are an early-access feature, off by default until a school configures its own encoder service — the school sets the encoder endpoint, so it can be scoped to the VPC you control, and the traffic is yours to inspect. Early access
Consent enforcementConsent handled in the sales/ordering flow. Not verified -- to confirm before publish.Consent is a database constraint, not a step in a sales flow — the sale path is gated on a consent record you can inspect in the schema of your own deployment.
Who gets paidSchool fundraising / commission programs offered. Not verified -- to confirm before publish.A four-way split that pays the school a named cut. Final split percentages pending
Picture-day operationsA national operator with its own logistics. Not verified -- to confirm before publish.A dispatch and scheduling operator product runs picture-day operations end to end.

Pholio vs. the cloud school-photo platforms

Pholio vs. the cloud school-photo platforms -- incumbent cells marked 'Not verified' need confirmation before publish.
DimensionThe cloud school-photo platformsPholio
Hosting / data locationA cloud platform. Not verified -- to confirm before publish.Self-hosted: the deployment runs in a VPC you control, so where photos are stored — and what the service is allowed to reach — are yours to configure and audit.
AI face-find on minorsNot verified -- to confirm before publish.AI face-find and match are an early-access feature, off by default until a school configures its own encoder service — the school sets the encoder endpoint, so it can be scoped to the VPC you control, and the traffic is yours to inspect. Early access
Consent enforcementNot verified -- to confirm before publish.Consent is a database constraint, not a step in a sales flow — the sale path is gated on a consent record you can inspect in the schema of your own deployment.
Who gets paidNot verified -- to confirm before publish.A four-way split that pays the school a named cut. Final split percentages pending
Single student recordNot verified -- to confirm before publish.Every portrait ties to the single student record — consent, sale, and roster in one place.

Pholio vs. the studio-storefront SaaS

Pholio vs. the studio-storefront SaaS -- incumbent cells marked 'Not verified' need confirmation before publish.
DimensionThe studio-storefront SaaSPholio
Hosting / data locationA cloud SaaS for studios. Not verified -- to confirm before publish.Self-hosted: the deployment runs in a VPC you control, so where photos are stored — and what the service is allowed to reach — are yours to configure and audit.
AI face-find on minorsA find-my-photos-style face match offered; cloud-run. Not verified -- to confirm before publish.AI face-find and match are an early-access feature, off by default until a school configures its own encoder service — the school sets the encoder endpoint, so it can be scoped to the VPC you control, and the traffic is yours to inspect. Early access
Consent enforcementNot verified -- to confirm before publish.Consent is a database constraint, not a step in a sales flow — the sale path is gated on a consent record you can inspect in the schema of your own deployment.
Who gets paidStudio-facing; the school-pay model Not verified -- to confirm before publish.A four-way split that pays the school a named cut. Final split percentages pending
Operator toolingA studio storefront + ordering tools. Not verified -- to confirm before publish.Dispatch, scheduling, and a clean roster tied to the single student record.

Verify it yourself

Every Pholio edge on this page is a design property rather than a promise, and you can hold us to each one — in a demo, or in your own deployment: where the software runs and what it is allowed to reach, the face-find feature (early access, off by default, pointed at an encoder endpoint you set), the consent constraint in the database, and the four-way split (percentages still early). Book a walkthrough and ask us to show it, not say it.