About
Guglielmo P.
Guglielmo P. is a software architect and the founder of PeakCore LLC, an independent studio that designs, builds and secures production systems. He works alone and end to end: the architecture, the code, the identity layer, the hardening and the automation that runs it afterwards.
What the work actually is
Most engineers do one of three things well: they architect systems, they attack them, or they automate them. This practice sits on the intersection of all three, and that is the whole proposition. A system designed by someone who has spent time breaking systems is built differently, and a system built by the person who will automate it is shaped for that from the first commit.
Everything below is a system that exists and runs. Nothing here is a proposal.
Systems built
Six production systems, each with its own page describing how it was built and what the decisions cost.
ReelVance
An autonomous short-video engine: it discovers a subject, writes the script, produces the video and publishes it, with a paid console on top.
First-party OAuth publishing to Google, TikTok and Meta, a credit ledger, a cron daemon and an MCP server. It runs five of my own social accounts unattended.
SocrateOS
A cognitive operating system built for 1o1.org: dialectic chat, a persistent actor identity, a cognitive memory graph and a multi-persona board.
Delivered milestone by milestone as technical partner, alongside MIT students on the client side. The client left a seven-paragraph public review.
PeakCore Auth
An OAuth 2.0 identity provider written from scratch, with PKCE and refresh token reuse detection, serving every application under PeakCore.
Not a wrapper around a hosted provider. The token lifecycle, the rotation policy and the reuse detection are mine.
AiGrow
A SaaS growth platform taken from an 8 out of 10 risk posture to a 2 out of 10.
React front end, Express and PostgreSQL API, authenticated through PeakCore Auth, with an auto-blogging engine added in July 2026.
HackerSuite
An offensive security lab organised around a 22-phase playbook, from reconnaissance through to reporting.
Built to run assessments end to end in an isolated environment.
Guglielmo Brain
A personal operating system that documents my own work automatically instead of asking me to write it down.
The record every page on this site is checked against before it is published.
Where the security work comes from
Smart contract auditing: reviewing deployed code where a mistake costs money directly, publicly, and without a rollback. Six protocols across staking, randomness, lending and a cross-chain bridge, some engaged directly and some through bounty programmes and a public audit contest.
The protocols are not named here, and neither are the findings: that is the condition the work was done under. What carries over is the habit it builds. Code that holds value is read as though someone is already trying to break it, which is a different way of reading than looking for bugs, and it is why hardening is part of a build on this site rather than a phase after it.
Before PeakCore
From 2022 to 2025 he built and ran the technical and community infrastructure of the Alexander Furrier ecosystem: a professional community that reached 40,000 members, a trading community whose partnership with the prop firm THE5%ERS distributed 3,000 evaluation accounts, and ReelsBuilder, an AI short-form video platform he ran as CEO. Web platforms, affiliate systems, staff tooling and Discord infrastructure, across all of them.
He is self-taught. Everything past a secondary diploma in computer science was learned by building things that had to work.
Questions
- What does Guglielmo P. do?
- He designs and builds secure digital infrastructure and then automates it with AI. In practice that means taking a platform from an empty repository to production on his own: the architecture, the code, the identity layer, the hardening and the automation around it.
- Is this a person or an agency?
- One person. PeakCore LLC is the company every project ships under, and Guglielmo is its founder and its only engineer. Collaborators are brought in for specific pieces of work.
- What makes this different from hiring a development agency?
- An agency separates the person who designs the system from the people who write it. Here they are the same person, which removes the translation layer where most of the cost and most of the defects live. The trade is capacity: one person takes on a small number of engagements at a time.
- How does an engagement actually run?
- In writing, asynchronously. A written brief in, a working deliverable out, agreed milestone by milestone. There are no standing calls, which is deliberate: it keeps the whole record of a project readable and searchable instead of trapped in meetings.
- What is the security background?
- Application and infrastructure hardening in production, plus smart contract auditing: six deployed protocols across staking, randomness, lending and a cross-chain bridge, some engaged directly and some through bounty programmes and a public contest. The protocols and the findings stay unnamed, which is the condition that work was done under.
Read how each of these was built, or the writing behind the decisions.