Privacy-respecting analytics

Joh uses Google Analytics to understand which stories and portfolio pages are useful. Advertising storage stays off. Read the privacy notice.

Joh Azores

Products, tools, and reusable engineering knowledge

Turning repeated technical work into useful products.

This is the home for my starter kits, WordPress products, AI tools, APIs, templates, open-source work, technical resources, and future courses. Every item is labeled by its real stage so visitors know what exists today and what is still being validated.

Planned product

Founders and product teams

Next.js business platform starter

A practical starting point for dashboards and SaaS products with authentication boundaries, roles, settings, CRUD, uploads, email, audit records, responsive layouts, and deployment guidance.

Join early access
Planned product

Plugin teams and agencies

WordPress product engineering toolkit

Reusable patterns and documentation for modern plugin interfaces, API integrations, migrations, background work, licensing boundaries, support workflows, and maintainable releases.

Register interest
Open-source prototype

Support and product teams

AI support workflow platform

An exploration of human-reviewed AI support workflows, knowledge context, operational safeguards, and practical automation without removing accountability.

View repository
Lead resource

Technical founders and engineers

Architecture audit playbook

A focused checklist for reviewing product architecture, code health, UX, performance, security, delivery risk, integrations, operations, and the highest-value next actions.

Request early access
Exploration

Developers and technical teams

Developer APIs and utilities

Small APIs, migration tools, integration helpers, and focused utilities created from repeated real-world engineering problems rather than generic feature collections.

Explore GitHub
Available

Companies and developer communities

Open-source sponsorship

Support maintenance, documentation, examples, integrations, and continued development of useful public projects or sponsor new work aligned with developer needs.

Discuss sponsorship

Product standard

Build from evidence, not from a long feature list.

Solve a repeated problem already seen in real engineering work.

Start narrow and understandable before adding integrations or tiers.

Use honest status labels and never present prototypes as mature products.

Prefer useful documentation, examples, and support over feature volume.

Validate demand before building billing, licensing, memberships, or marketplaces.