Delivered (Currently Alpha Release)
34Under consideration
[NEW] Added registration / login based on Auth0
Automated resolution of Hypertube Dependency from Graftcode Registry for other than Nuget technologies
With this improvement whenever you pull Grafts with any Package Manager other than Nuget you will not need to explicitly pull the Hypertube dependency (currently you need to manually make i.e. npm install javonet-nodejs-sdk prior to any graft resolution)
Release of the Authorization header support
With this release we are planning to provide support for HTTP headers for edge client connections based on HTTP/2 or Websocket channels allowing for passing any header related information as well as Authorization header with either JWT, Basic, API Key etc.. and full support of injecting this state into standard HTTP context on called side allowing for Authorization headers functionality
Support for using calling technology classes wrapping value types (i.e. Date)
Now calling technology will be able to use local classes that wrap value types like Date, Color, Point and passing them to target service or runtime will automatically convert them to target technology wrappers by passing value of ticks, Hex, X,Y etc…
[NEW] MCP Protocol Support!
Any logic hosted on Code Gateway can instantly be consumed also through MCP JSON-RPC requests (from LLM Chat)
Support for TCP/IP Protocol
In addition to Websocket Secure presented in PMF demo, November release introduces full support for direct TCP/IP TLS channel.
Removed all dependencies required to install Graftcode Gateway
With this release Graftcode Gateway on all platforms will be installable without the need to install any prerequisite dependencies.
Grafting async methods to async grafts
With this capability method with async will graft as async and will allow for invocation over sync or async channel correctly translating code to real transport
Grafted Service Discovery Endpoint
With this feature Graftcode vision will start exposing standardized path where AI Agents and developers will be able to technically test if service is grafted and will learn structure of methods exposed and install commands for grafts per each tech.
Add cors parameter to Graftcode gateway
Allow configuring cors for graftcode gateway so it’s sent for http/2 preflight options or validated for websocket
Coming Next (Upcoming Beta Release)
19Committed and queued
Enhanced logging - Full support for OpenTelemetry Monitoring and Observability with TraceID and SpanID
Now you will be able to pass custom logger to imported Graft and it will be used to report all operation on Graft, logs from sending request and retrieving results. Graftcode Gateway will support custom loggers too allowing you to continue logging on server side up to your business logic preserving Span and Trace so all logs will be fully correlated.
Self-hosted Grafting Engine Available in Cloud Marketplaces
With this feature you will be able to deploy self-hosted grafting engine wihtin your own cloud and pay with cloud bill
Support for Fire and Forget calls
With this feature if attached queue is in pub/sub or fun-out mode specific method calls potentially void only you will be able to invoke in fire and forget pattern.
Information about non-graftable types and proposed filters for graftable API on console and discovery endpoint
With this feature your AI will learn if your module has non graftable apis and will get simple command how to run GG with only graftable API filter.
Ability to set authorization and other headers in Vision
With this feature you will be able to set headers that will be passed to all the calls from Vision to Gateway so you can append your own JWT token.
Support for Delegated Authentication to MCP tool
With this feature you will be able to easily plugin authentication mechanism for MCP so people can get their AI delegate them to OAuth page that will grant the client access to MCP tools hosted on Graftcode
Starting Graftcode Gateway from currently running process
With this feature graftcode will allow to expose graftcode endpoints without launching server on GG but instead adding graftcode as project dependency and starting it from the runtime of process launched on another middleware or app server.
Support for Grafting stream and multi-out result
With this capability Graftcode will support grafting and keeping connected streams returned between runtimes and allow for multi out writes to client.
Code Signing for Graftcode Gateway
To ensure smoother download and pass through OS gatekeepers for our Graftcode Gateway we are planning to start signing the binaries to increase filter trust.
Use Cases Dedicated Landing Pages in HomePage
With this feature Graftcode.com will show you all the details per each critical use case where you can apply graftcode.
Mid-Term
10Actively being built
Env variables for overwriting external host and external ports for GV
With this feature you will be able to set for your containers external host and port that will be used on graftcode vision so your end consumers will immediately use the right host visible publicly instead of localhost visible to container.
Support for mTLS
With this feature Graftcode will allow you to use mutual TLS authorization.
Greedy Filter and Missing type message
With this feature Graftcode Gateway will notify on console if your filter exposes class that references other types which are not exposed yet in filter. You will have option either to add them as error will explain OR use greedy filter which pulls all references automatically.
Sample Real Production Project in Each tech pair
Our Academy will start presenting sample projects with frontend, jwt authentication, stateless backend, and queue between microservices, exposed public api and dependency injection and mixed modules in specific services so you can easily apply graftcode into your project. All of that with great OpenTelemetry support. Sample will show also signalR like bi directional connection and streaming sample.
Examples with complex objects in stateless in arguments and results as part of quick start guide
With this quick start guide will show you how to work in stateless with complex objects. It works now but good sample is worth more than promise ;)
CLI for generating grafts
tool for generating graft for local library without hosting it on graftcode gateway it will support polyglot monolith workflows to get locally command to install package via graft to allows future decomposition or to host multi tech in one process irm grft.dev/graft | iex backend.dll
Support for Swift and Dart
Critical KPIs at Hand
You probably realized the KPI coming soon section on the dashboard this one will soon become enabling giving you quick access to aggregated data how many gateways are running for your project, how many modules are hosted and grafts generated. KPIs also estimate for your how much dev time/AI tokens you saved and less CO2 generated thanks to using Graftcode in your projects.
Environments Support
As usage of graftcode grows and you setup more and more of your not only POC DEV environments but also TEST and PROD solutions we are planning to add tags allowing you to mark which gateways are production or TEST environment and filter properly all views and controls in portals.
Guarantee Backward Compatibility for Grafts, Protocol and Gateways
With first stable release we will switch to backward compatible releases plan so every new Grafting engine will support old versions of Gateways (starting with first stable release), all changes to Hypertube will ensure backward compatibility with older version of calling side as well as compatibility of SDK exposed to Graft with previous hypertube versions so every existing Graft can be safely used with any future release of Hypertube.
Long-Term
14Recently shipped
Support for grafting REST API based on openApi
With this feature you will be able to start using graftcode EVEN IF your backend service or third-party API is not yet on graftcode and still uses legacy technologies like REST.
Support for grafting events and allowing to subscribe them remotely
With this feature graftcode will start grafting events and delegates allowing client in statefull mode to subscribe to server side and keep getting notified whenever event or delegate is triggered achieving full bi-directional SignalR like real-time communication.
REST pass-through
With this feature you will be able to add graftcode.gateway as dependency to your existing REST enabled project (ASP.NET MVC, Spring, Flask) and route selected path like POST /graft payload directly to graftcode interpreter for Graftcode related processing. In this way you can co-host stateless graftcode functionality within your existing REST interfaces endpoint.
Add support for exposing directly Databases with RLS instead of modules via GG
With this feature GG will allow you to point database connection string instead of modules and Graftcode will automatically expose CRUD operations protected with RLS to specified target database.
Adding Graftcode Gateway as project dependency
With this feature, you will be able to add graftcode gateway as project reference (in .NET, Java, node, ruby, php etc..) and initialize it from your starting class in your project similar to regular REST framework like spring, flask, asp.net mvc. GG will automatically extract and load into memory required native components preserving your launch command the same as before using graftcode.
Provide GG as managed code dependency
With this enhancement for single runtime use case you will be able to add and use Graftcode Gateway as your project dependency and keep your root process untouched. There will be possibility to set it up at startup of your app in code.