Przemysław Ładyński

CEO at Graftcode, Creator of Javonet, Co-founder/CTO at SdNcenter, Software Engineer, Software Architect

[Przemysław Ładyński @pladynski]

@clankenluben @grok @Graftcode @grok am I right?

[Przemysław Ładyński @pladynski]

External third party can pull the graft with regular package manager from any tech: pypi, Nuget, npm, maven, packgist without any special configuration or tools. The package they pull will stay always up to date whenever you publish new version of api as long as don’t fix specific version in dependency file.

This in fact makes you public apis much easier to be consumed by third parties with no need for docs to read.

If they do it will keep working with old graft as long as you make no breaking changes (it’s the same for any other approach).

Graftcode is free and planned to be release under BSL license with open source protocol that we aim to pass to cloud native foundation.

Interoperability: works any tech mix, in memory and remote, allow to switch from monolith to microservice with zero code change or replace service bus with amazon sqs also just via config

Observability: full open telemetry support with standard exporters from app insights, data dog, grafana etc…

Backward compatibility: your api becomes natively versioned by client modules and strongly typed checked and compile time. And old grafts work with newer api

Maintainability: your code becomes business logic plus simple plain classes and public methods facade that can serve any protocol, web sockets, http/2, queues, mcp with zero coupling to any specific tech. Your code base is clean, client has always up to date strongly typed module and ai don’t need to ingest, analyze and generate any piece of integration specific code making your PRs much cleaner

Independent deployment has one tradeoff. You can strongly typed clients and easy update of api and backward compatibility with enforced versioning for the price that you cannot write client before having at least mock of facade (we work on it).

If Graftcode disappears it becomes open source it’s aimed for that direction anyway. And as you did nothing special for Graftcode you just write your legacy controllers or proto idl which you had a pleasure to skip and get back to old fashioned coupling to integration layer code.

[Przemysław Ładyński @pladynski]

@clankenluben @Graftcode @grok is this guy right?

[Graftcode @Graftcode]

New video is live: connect Angular to a backend with Graftcode.

Learn how to install a Graft (a strongly typed client from your package manager) and call backend methods from your Angular app as local code.

https://t.co/SfjPzdRXuy

[Graftcode @Graftcode]

We're not really sure what to do with all this time on our hands now... please help.

Tired of wasting tokens on integrating and maintaining your services? We'd be too, but our services are grafted so we ain't got that problem

Save your time and money see the new way of integrating services -> https://t.co/oIubvox2Ub

[Przemysław Ładyński @pladynski]

Guys is Graftcode better version of gRPC?

[Przemysław Ładyński @pladynski]

Cool!

[Graftcode @Graftcode]

Want to connect React with a .NET backend without writing REST APIs or API clients?

🎥 Watch the tutorial: https://t.co/PwrYWGTjDa

#React #dotnet #WebDev #Graftcode #FullStackDevelopment #SoftwareEngineering #DevTools

[Przemysław Ładyński @pladynski]

Really?

[Graftcode @Graftcode]

Want to connect React with a .NET backend without writing REST APIs or API clients?

🎥 Watch the tutorial: https://t.co/PwrYWGTjDa

#React #dotnet #WebDev #Graftcode #FullStackDevelopment #SoftwareEngineering #DevTools

[Przemysław Ładyński @pladynski]

Check this!

[Graftcode @Graftcode]

Want to connect React with a .NET backend without writing REST APIs or API clients?

🎥 Watch the tutorial: https://t.co/PwrYWGTjDa

#React #dotnet #WebDev #Graftcode #FullStackDevelopment #SoftwareEngineering #DevTools

[Graftcode @Graftcode]

Want to connect React with a .NET backend without writing REST APIs or API clients?

🎥 Watch the tutorial: https://t.co/PwrYWGTjDa

#React #dotnet #WebDev #Graftcode #FullStackDevelopment #SoftwareEngineering #DevTools

[Graftcode @Graftcode]

😂 Frontend & Backend are in couples therapy!

Therapist: “How many layers are between you?”

Frontend: “DTOs, mappers, API gateways…”
Backend: “And don’t forget versioned endpoints!” 💀

Then comes Graftcode: What if your frontend could call backend methods like local functions? 👀

Less boilerplate. Less drama. More shipping. 🚀

🎥 Watch the therapy session 👇
https://t.co/P3et2hhG7N

#WebDev #Frontend #Backend #Graftcode #API #SoftwareEngineering #DeveloperHumor

[Przemysław Ładyński @pladynski]

@Graftcode That’s how everyone should integrate 😂

[Przemysław Ładyński @pladynski]

https://t.co/cGQ77eg6Zz

[Graftcode @Graftcode]

AI made code cheaper.

So companies are building more of it.

Cost per feature ↓
Total software spend ↑

The Jevons paradox, applied to AI-assisted dev 👇

[Graftcode @Graftcode]

What a great day at THE MOAT by Hard2beat! 🚀

Our founders @pladynski and Łukasz had the opportunity to showcase Graftcode with a live demo on stage and connect with investors and founders from across the ecosystem.

#Graftcode #THEMOAT #Startups #EnterpriseAI #DeveloperTools

[Przemysław Ładyński @pladynski]

https://t.co/dy9pioLRZh

[Przemysław Ładyński @pladynski]

Any simpler way to get MCP?

[Graftcode @Graftcode]

Your next AI tool might already be in your backend.

Graftcode turns exposed public methods into MCP tools—without hand-written tool wrappers.

What would you let an AI agent call first?

See how: https://t.co/SnnrT3TJ54

[Przemysław Ładyński @pladynski]

That is really easy!

[Graftcode @Graftcode]

The Graftcode YouTube channel is live!

Explore hands-on demos of strongly typed communication, cross-language execution, microservices, and AI agents through MCP.

Less integration plumbing. More building⚡

▶️ https://t.co/oHyPCyevsf

#DeveloperTools #AIEngineering #AIAgents

[Graftcode @Graftcode]

The Graftcode YouTube channel is live!

Explore hands-on demos of strongly typed communication, cross-language execution, microservices, and AI agents through MCP.

Less integration plumbing. More building⚡

▶️ https://t.co/oHyPCyevsf

#DeveloperTools #AIEngineering #AIAgents

[Przemysław Ładyński @pladynski]

@IamAroke Graftcode!