Jeremy Daly Portfolio
Independent consultant; building Ampt
Independent cloud and AI consultant, AWS Serverless Hero and builder of Ampt, writing the "Off-by-none" newsletter on cloud architecture and serverless systems, with over two decades of production infrastructure experience behind the analysis.
Location
Location: classified. Send a pigeon.
Skills
What makes it work
A breakdown of the choices that make this portfolio stand out.
A named newsletter with a stated multi-year run
"Off-by-none" gives the writing a consistent home and a track record readers can scroll back through, rather than scattering architecture takes across one-off posts.
Career transitions reflected honestly on the site
Documenting the move from independent serverless consultant to Director of Research at a cloud cost company shows a real, traceable career arc rather than a static "expert" label frozen in time.
Commentary that tracks where the industry is actually heading
Recent writing on "post-serverless" and AI-native infrastructure shows the author revising his own prior positions as the field changes, rather than defending one architecture style indefinitely.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Give your recurring writing a real name and stick with it for years — a named, dated newsletter reads as more credible than an unlabeled blog.
Let your site show your actual career arc, including job changes — a visible trajectory is more convincing than a single frozen bio.
Be willing to publicly revise an earlier architectural opinion as the field moves — it signals judgment, not inconsistency.
Case studies
A weekly newsletter, two AWS libraries that are still maintained, and a startup built on Infrastructure-from-Code. Jeremy Daly's portfolio shows a serverless architect writing about the ecosystem, shipping tools for it, and building a company on it.
Off-by-none (newsletter)
A weekly email on the technical details of building cloud applications serverless-first, sent every Tuesday. Each issue collects articles, tutorials, tools, use cases and industry news, with Daly's commentary on top. Lately it covers AI infrastructure alongside AWS releases.
Curating and commenting on the serverless field every week for years means he has tracked it closely. The recent move into AI infrastructure shows the curation moving with the industry.
371 issues; recent ones cover Lambda MicroVMs, CloudFormation speed-ups, AWS Blocks
Published every Tuesday per the About page
Public issue archive plus a 'Cloud Quiz' on the same site
Projects
A lightweight web framework built specifically for AWS Lambda and API Gateway. It handles routing, HTML and binary responses, redirects, middleware and error handling, and has a built-in logging engine that can sample requests. It parses API Gateway proxy events and formats responses so handler code doesn't have to.
It is a framework designed around Lambda's execution model instead of an Express port. The README's argument about how big a 'single purpose' function should be shows architectural judgment.
Built for Lambda Proxy Integration: request parsing and response formatting handled
Built-in logging with periodic request sampling for tracing and benchmarking
1.5k stars, 127 forks, 41 tags
Data API Client
A 'DocumentClient' for the Amazon RDS Data API. It wraps the raw API's typed-parameter requests and nested responses in a simple query method with named parameters and chained transactions. v2 added compatibility shims that impersonate the mysql2 and pg drivers, so ORMs can run over the Data API. v2.4 adds a Prisma 7 adapter.
Driver-compatible shims over a non-TCP protocol are careful interface work. They let existing ORMs run on a serverless-friendly database API unchanged.
Drop-in shims matching the mysql2/promise and pg interfaces
Prisma adapter in v2.4, alongside Knex, Drizzle and Kysely
Works on Aurora Provisioned and Serverless v2, Postgres and MySQL
Ampt
A platform that provisions, manages and optimizes isolated AWS environments for JavaScript apps. A runtime introspector reads the app's code and configures the cloud resources it needs. Daly calls its two main ideas Productized Patterns and Infrastructure-from-Code (IfC).
Founding a developer platform means making the architecture choices on behalf of every customer. His candid post about competing with better-funded tools is useful product experience.
Infers cloud resources from application code (Infrastructure-from-Code)
Fully managed, isolated AWS environments per app
Founder's own retrospective on the product published on jeremydaly.com
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.