Skip to content

Aboard Foundry

We’re constantly exploring the possibilities AI is bringing to software development. Foundry is our hub for sharing experimental and innovative home-grown projects. Some we use in our work every day. Some are experiments we think are just plain cool. Check out what we can make.

Aboard Sign

A signing tool that forgets your contract when it’s done

Signing documents electronically is a pain, and we wanted to make it a little bit less painful. So we made Aboard Sign. It works entirely by email: attach your document, send it to whoever else needs to sign, and Cc sign@aboard.com. Everyone, you included, gets a link of their own, signs, and receives the signed PDF. Then everything is deleted from our server. That's it! Where's the official record? Well, the PDF carries its own proof: a fingerprint on every page and a cryptographic key for every signature. Nobody needs us to keep a copy to show it’s real. It's yet another example of Aboard working together to deliver useful things to the world quickly. Try it yourself!

  • Led by: Rich Ziade
Technical addendum
How it starts
Email is the only way in. Send a Word, PDF, RTF or Markdown file to sign@aboard.com with the other signers on Cc. The subject line becomes the title. Aboard Sign replies to each person in the same thread with their own link.
Built on
TypeScript on AWS. CloudFront sits in front of Lambda functions for the site, the API, incoming mail, outgoing mail, and a cleanup job that runs every 10 minutes, all deployed with SST. DynamoDB holds signings and the public log, and S3 holds documents and signed copies, encrypted. Mail comes in through Amazon SES and goes out through Resend. Word, RTF and Markdown files become PDFs through a typesetter we wrote just for Aboard Sign.
Where AI did the work
Claude Code wrote the code. Every commit in the repo is co-authored by Claude.
Where humans did the work
The team made the product decisions (they’re logged in the repo), designed it, wrote the copy, and took it to production. Then came the loop: people tried what Claude built, sent notes, and Claude made the changes. The commit history is round after round of design notes, reviews and copy edits.
Logging in?
There’s no login. Your link is your login. When you open it, your browser makes a signing key of its own that can’t be exported. Links work for 72 hours; open one later and you’ll get a fresh one by email.
Where it saves
Everything after the “#” in a signing link is a key, and browsers never send that part to a server. That key encrypts the document, the names, the signatures and the sender’s note with AES-256. Everything else, like addresses and the title, is encrypted under a key the server holds. When everyone signs, or 30 days pass, it’s all deleted, and anything left in storage is wiped after 40 days. The signed copy can be downloaded for seven days.
What the server sees
The server does hold the link key, briefly. It needs it to send the links and again when the last person signs, so it can build the signed PDF. It never saves the key, but the key travels in the emails. So it’s encrypted at rest, not end to end.
The signed copy
Every page carries its own SHA-256 hash, printed at the foot of the page, and that's what the document’s fingerprint is built from. Each signer’s key signs the fingerprint and every page. The server countersigns each signature with its own published key and adds the time. On top of that, the whole PDF carries a standard PDF signature (PAdES), timestamped by DigiCert and locked against edits. Standard PDF tools see it as signed and unchanged. Our certificate is self-signed for now, so viewers like Acrobat won’t vouch for who sealed it by default.
Checking a copy
Drop a copy on the record page and the whole check runs in your browser. It re-hashes every page, checks every signature and the seal, and replays the signing record attached inside the PDF. The file never leaves your browser; the page only looks up its fingerprint in the public log. For the extra cautious, there’s a standalone verify page that makes no network requests at all.
The public log
Every completed signing gets one permanent entry: an id, the fingerprint, the page count, the time and the signed PDF’s hash. There are no names or titles. Each entry includes the hash of the one before it and is signed by the server, so the log can only grow. A copy goes to a public GitHub repo every day as an outside witness: github.com/aboard-io/aboardsign-log.
Spoofing
An email only starts a signing if it passes mail authentication (DMARC, DKIM or SPF). And since everyone signs, the sender too, from a link mailed to their own address, a faked sender can’t finish a signing without the real one. What it can’t stop is someone who’s actually in your mailbox.
Agents
An AI assistant can read plain-English instructions at /llms.txt, or the formal spec at /openapi.json. It can start a signing from a document it wrote and hand you your link. It can also ask the API whether a signed copy is legitimate.
Limits
Up to 10 MB and 100 pages per document, and five people per signing, sender included.
Legal standing
It’s an electronic signature under the US ESIGN Act and UETA, and a “simple” electronic signature under eIDAS in the EU and UK. It’s not for wills, family law, court papers, or anything that needs a notary.
Tradeoffs
Your identity is proof that you can open your email, not an ID check. The signed PDF holds everyone’s names, emails and signatures, so whoever has the file can read them. Mail providers keep mail the way they always do. It keeps almost nothing, not nothing.
License
The code is private for now; the public log is public. It’s built with open-source pieces (pdf-lib, pdf.js, Lit) and fonts under the SIL Open Font License.
All the info is on our handy site, sign.aboard.com
Email your document, and Aboard Sign replies with your link.
Read before you sign.
Type or draw your signature.
Every signature, with its key, on the last pages.
The certificate travels with the copy.
Every page has its own fingerprint.
Check any copy without uploading it.
The public log: fingerprints, no names.

TinyLittleOffice

An office suite where the link is the document

Making a one-page flyer or a quick budget shouldn't require an account, a cloud drive, and a company reading over your shoulder. Six years ago Rich Ziade built TinySheet, a little spreadsheet that kept its data in the URL; it was followed by TinyCalendar, and then we moved on and the old links broke.
This year Paul Ford picked the idea back up and, working with Claude Code, grew it into a ten-app suite: word processor, slides, outliner, spreadsheets, drawing, diagrams, animation, calendar, trip planner, and more. Every document lives in the part of the URL address after the #, which browsers never send to a server, so the link is the document: copy it, paste it into chat, or print it as a QR code.

Technical addendum
Where it saves
There was absolutely nothing saved to a server. (When you put stuff after “#” in a URL, it stays local by default.)
Sharing
Copy the URL and paste it into chat. Now everyone in the chat has a copy they can edit. All your ISP can see is that you visited a site—the data is in the link.
Exporting
Export it as a document—PDF, PowerPoint, Markdown. Or as a QR code. If the document is a page or two long, the QR code can contain the whole document.
Shorter links
Shorten the URL if it’s a bigger doc by saving it to our URL shortener. Your browser encrypts the document and sends that to a server. The “key” is in the link, after the “#”—so the server never sees what you saved. (All links expire, maximum duration is a month.)
Tradeoffs
The links can get unwieldy pasted in chat, and you can’t upload video or images, full stop. It’s not collaborative like Google Docs. It’s collaborative like handing out zines at a street fair.
Agents
It was built to make sense to agents—you can tell an LLM to check out TinyLittleOffice.com and use it to make small, shareable things.
License
This project is open source with the MIT license.
So tiny, so free.
It is simply simple.
You decide how private you want your documents to be.
Maybe make a tiny presentation.
A tiny document can do big things.
Charts are calming.
Oh sweet Sankey.
Shapes!
Make it make sense.
Keep a tiny calendar.
We global.
Make a QR code, it's the document, too!

Evo

A tool that reflects our principles: careful planning, accelerated with AI

Evo is Aboard’s internal staff portal, the place where everyone at the company starts their day. It replaced a patchwork of paid tools and shared documents: Airtable, Greenhouse, email for expenses, and on and on. Employees use Evo to log standups and time, set their status, book desks and rooms, file expenses, track to-dos and goals, share vaults, and more. Managers get a second layer on top: project staffing, talent and recruiting, performance reviews, and reporting. Today about 95% of the company opens Evo every day, and it has saved the company thousands of dollars in subscriptions.

Technical addendum
Built on
Next.js 16 (App Router, React 19, TypeScript in strict mode), PostgreSQL via Prisma, NextAuth v5 for Google OAuth, Tailwind CSS 4, Redis caching, and Vitest for testing, deployed on Railway — with integrations into AWS S3/Bedrock, Slack, and Google Calendar.
Where AI did the work
Evo’s codebase is 100% AI-written under human guidance and review. By rebooting the project with an AI-first project, Evo is now highly adaptable—new features, guided by requirements and tests, are simple to implement and deploy.
Where humans did the work
While AI wrote a lot of code, the very human team defined requirements and defined the platform architecture. In addition, every database and API pull request is manually reviewed before merging; nothing ships on AI output alone.
Security
Evo’s API is fully closed: the only way in is Google OAuth through a 2FA company account. The credential vault uses strong, current encryption. Every database and API change goes through manual review, backed by manual penetration testing and AI-assisted review agents.
Evo opens on your day: whether your standup is in, how much PTO you’ve used, who’s out, who’s in the office, and what’s coming up.
Each morning, people split their day across projects by percentage and write a short standup. Anything under 100% shows we have room to take on more.
Everyone on a project can read the team’s standups in one place, with each person’s time on the project beside their name.
Vacations, business trips, sick days, and conferences in one list, shown in your own time zone.
Holidays for each of our offices, company events, and who’s away, all on one calendar instead of added by hand.
Book a desk on a map of the office and see who else is coming in that day.
Company-wide to-dos, assigned from one person to another with a priority and a due date. Before Evo, no tool we paid for did this.
Submit an expense with a receipt and a project, then follow it from submitted to reimbursed. This used to happen over email.
The org chart, with roles, reporting lines, and permissions kept in one place.

Cadence

Our AI-driven product delivery workflow, from the first research to shipped code

Cadence is Aboard’s custom project-management and collaboration hub, and the AI-driven product delivery workflow behind our projects. Everything about a project lives in one place: the research, the feature specs, the prototypes, the milestones, and the tasks that build it.

Projects move through the same stages every time. We define the work first: the landscape, what we discovered, and the solution. Then we deliver it: feature specs set out what gets built, milestones sequence it, and tasks implement it.

Each task is built by a pipeline of AI agents, in a sandbox of its own: a planner, a coder and a reviewer, then QA, design and security passes, each checked against the task’s scope and acceptance criteria. The team gets the work back with a live preview to look at.

Technical addendum
Built on
A Hono API on Bun, a React 19 app with TanStack Router and Query, Drizzle ORM on PostgreSQL, Graphile Worker for background jobs, Better Auth, and ElectricSQL for realtime sync, with Anthropic or OpenAI models through the AI SDK. It runs on AWS.
The build pipeline
Every task runs in its own AWS Fargate sandbox. The planner maps the task to a plan, the coder implements it, the reviewer reads the diff against the scope, QA verifies each acceptance criterion in a real browser, the design pass hunts visual defects, and the security pass looks for authorization and ownership bugs in the app being built.
Containment
Cadence builds and runs other applications, so its sandboxes are built to run anything. The work is keeping each one contained: away from other projects, away from Cadence itself, with previews served on isolated hosts.
Connected
GitHub for code, Sentry for errors, and a command-line tool that lets the team work with Cadence from the terminal.
Every project has a home that grounds you in your next task based on your project status
Cadence is a tool coupled with a process, rooted in deep product work. Instead of jumping right to code, it walks you through deep discovery, research, and design thinking.
Threads, or your agentic thought partner, guide you through the entire process. Summon a thread anywhere to ask questions about your codebase, start a coding session, do web research, or all of the above
After discovery and definition, Cadence walks you through writing rich specs, the foundation of functional features.
Milestones are your roadmap, and Cadence will agentically work through the feature specs until a milestone is complete.
You can always ask Cadence for a progress report and it will update you about everything the team has worked on.
Milestones and specs are user-facing, but to turn them into code, Cadence breaks down the work into Build tasks.
Every task gets dispatched in a logical order to an agent running a full virtual sandbox, or you can work collaboratively with the agent before opening a pull request. Cadence agents write production-quality code, complete with robust test suites, automated code review, and even visual design QA. And every task gets its own preview link you can check out yourself or share with your team.
Want to explore creative design ideas? Start a prototype session, and Cadence will spin up a live version of your whole application, and you can iterate on new concepts and features.
Once you’re happy, share the link to the working software for feedback or ask Cadence to open a pull request.