Private context. Public standards.
A cockpit for life, archives, automation, and publishing.
Diary Suite connects Diary, Dossier, Home, DAM, GAS, Hub, Reach, Brand, Lab, and Academy: a disciplined way to preserve memory, understand context, operate homes, govern media, automate work, publish cleanly, communicate with evidence, and turn knowledge into learning.
Capture
Classify
Preserve
Automate
Publish
Cockpit Central
The Windows command surface for every Diary Desk and Pulse.
Cockpit Central brings desks, pulses, workflows, files, API status, deployment checks, and self-healing signals into one visible operating surface.
One portfolio, eleven products
Each lane has its own job, but they work together as one operating model.
DiaryLife archive and workflow discipline
DossierPeople, conversations, and context
HomeSmart homes, presence, telemetry, and evidence
DAMMedia assets, metadata, and provenance
GASGoogle automation and API authority
HubWebsites, deployment, and product publishing
ReachChannels, publishing queues, responses, and signals
Why this exists
The world is messy. Diary gives it places to land.
Files, photos, trips, homes, machines, contacts, scripts, APIs, and websites all become easier to trust when they have names, owners, versions, and visible rules.
Creator Editorial
Built by someone who needed calm structure to survive real life.
I built Diary because private life produces more evidence than memory can responsibly hold. Photos, conversations, trips, homes, scripts, APIs, and websites all deserve structure before they become noise.
Diary preserves lived proof. Dossier keeps people and context readable. Home turns property signals into operations and evidence. DAM protects media and metadata. GAS automates the parts that should not depend on memory. Hub makes reviewed surfaces publishable. Reach governs communication and response. Cockpit Central is where all of that becomes visible enough to operate.
The goal is not more noise. The goal is a calmer operating model: authority where authority is needed, automation where automation helps, and human judgment where human judgment still matters.
Meet the Team
Two people, one AI teammate, and a working model for a life that moves.
Diary is personal by design. The public layer introduces the human and AI team behind Diary while the private evidence stays protected in Dossier.
Leopold Schmallegger
Creator and product owner of Diary, with a professional track across ERP, automation, archives, property operations, and web publishing.
Diane Schmallegger
Education, learning design, maker perspective, and real-world usability for products that have to work for people, not just machines.
Team AI
Codex-supported collaborator across Diary Desks and Pulses: translating human intent into cleaner software, better audits, readable pages, and practical Human-AI operating habits.
Public Network
Eight public sites, one operating logic.
The public Diary Suite network separates technology, real estate, travel, family history, and regional archives so each surface stays clear while still pointing back to the same Diary Suite.
SL
Schmallegger
The public home for Diary, its products, Desks, Pulses, team, proof, and privacy.
www.schmallegger.netPE
PoldiEstates
The public real-estate and 0R operations surface for a small, curated property lane.
www.poldiestates.comSW
SchmallWorld
The travel, stage, lifestyle, culture, and perspective lane.
www.schmallworld.netProof Signals
Early evidence from Diary Desks and Pulses, framed without pretending to be public customer testimonials.
Privacy first
The public site stays small by design. Sensitive archive work remains private unless explicitly published.
Cloud ready
Hub separates source authority, local Git working copies, and Cloudflare deploy roots.
Human readable
The work may be technical, but the public surface must remain calm, clear, and understandable.