victorteo

They are similar things. The wheels are reimplemented to suit Teo's architecture.

Thanks! I update it.

Hi @Terretta, I plan to generate OpenAPI output for HTTP clients like Postman to import and read. We have things like FastAPI, Starlet, pedantic, sqlmodel and Postgres in Teo. The only thing we lack of is the debugger web interface which we could use Postman after exporting OpenAPI output is implemented.

The logfire is pretty cool and in the future, it will be implemented in Teo's way.

The text is updated on the website. And it's not next-generation anymore.

Hi @hliyan, I will update the words.

Well, I just looked at Smithy. And they quite differ. Teo is just an HTTP framework like fastify, express, koa, flask and fastapi. It has a schema language and a builtin ORM, which make it quite similar to GraphQL and Prisma.

Hi @tkzed49, Teo supports custom route handlers and routing middlewares. Teo is a web framework with a builtin ORM. There are builtin permissions, too. You can use it or implement your own. Teo supports database auto migration.

I will remove the "next-generation" thing.

That makes sense. I fill fix panics and take this consideration into the next major version.

Both big projects and small projects are targeted. It doesn't sacrifice functionality while provides speed up.

Hi @e-clinton, it does have auth builtin.

Thanks! I will update the hero text.