Grafiesto / 02 products
Our own software
Grafiesto builds and operates two products of its own. PixoPie helps event guests find the photographs they are actually in. Bytescrap turns public pages into structured data. Both run in production — which is the only place an engineering standard is ever really tested, because we are the ones who get the support email.
Built in-house. Not white-labelled, not resold.
Two productsPixoPieFace-based event photo discoveryBytescrapWeb data extraction and analysis
Both products
Neither product started as a market opportunity. Both started as a job somebody was doing by hand, badly, for hours — including us.
Face-based event photo discovery
PixoPie helps event guests find photos that may include them through a selfie-based matching flow.
Web data extraction and analysis
Bytescrap turns public web pages into structured data for research, monitoring, and analysis workflows.
Why we run them
An engineering standard is easy to hold in a proposal and hard to hold at eleven at night when the thing you shipped is the thing that broke. Running our own products means we never get to be the vendor who has already moved on.
A demo ends when the presentation does. A product has guests uploading a selfie on a phone with two bars of signal, and a support inbox that answers back. That difference is most of the work, and it is the part client pitches usually skip.
There is no separate product team here and no separate client team. What we learn keeping our own software up is carried by the people who then sit in your repository — which is the only honest way that knowledge ever transfers.
FAQ
Direct answers — the same ones search and answer engines look for.
Something more specific to your stack?
A senior practitioner replies directly — no ticket queue.
Grafiesto builds and operates PixoPie, a face-based event photo discovery product, and Bytescrap, a web data extraction and analysis product. Both are in-house products the studio runs in production, which is how it keeps its own engineering and operational standards honest.
Build one with us
Somebody on your team is doing a job by hand every week that should be software. A first conversation is thirty minutes, costs nothing, and ends with a written summary of what we think that job actually is.
