---
title: "Discussion on \"Introducing Massimo\" | Hashnode"
description: "Discussion on \"Introducing Massimo\". Today marks a significant milestone in the evolution of type-safe API development. What began as @platformatic/client in our v0.19.0 release has grown into something much bigger—a production-proven, enterprise-grade solution now powering companies li..."
url: "https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8"
---

[Feed](https://hashnode.com/feed) /

Discussion

[Matteo Collina](https://hashnode.com/@matteocollina)

Open Sourcerer, Node.js TSC member, Fastify Lead Maintainer

Sep 1, 2025

# [Introducing Massimo](https://blog.platformatic.dev/introducing-massimo?utm_source=hashnode&utm_medium=feed)

Today marks a significant milestone in the evolution of type-safe API development. What began as @platformatic/client in our v0.19.0 release has grown into something much bigger—a production-proven, enterprise-grade solution now powering companies li...

blog.platformatic.dev 8 min read

[#nodejs](https://hashnode.com/tag/nodejs) [#web-development](https://hashnode.com/tag/web-development)

## Responses 2

Markdown supported · ⌘↵ to post

[Cristian Ferrari](https://hashnode.com/@VOLTA)

[Sep 8, 2025](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68beed9a861dbd478c2dcc97)

As massimo means maximum, maybe you can use max as short command for the cli. BEST!

[Ignacio Lopezosa Serrano](https://hashnode.com/@nacholopezosa)

[Sep 2, 2025](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68b6f71e247042aa63186ea4)

Just to be completely sure. I guess it’s compatible with Next.js (server side and browser side) with the native fetch approach. Is it? Is there any catch?

[Matteo Collina](https://hashnode.com/@matteocollina)

Open Sourcerer, Node.js TSC member, Fastify Lead Maintainer

[Sep 2, 2025](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68b6f71e247042aa63186ea4#reply-68b702689e96f4ce75e7bbdc)

Yes, the native fetch approach is compatible 100% with Next.js. No catch, no dependencies.