Choose your scenario

Use this page to route from your goal to a Quick start course and the documentation that explains the design behind it. Graftcode is best suited to callable behavior with an intentional programming interface; it is not a universal replacement for every protocol or data movement pattern.

Note

Hands-on first: Quick start has step-by-step tutorials. Return here and to the reference pages when you need concepts, constraints, or operations detail. See the full course index in

Quick start courses.

Start with your goal

Pick one of the five integration scenarios below, then open the matching section for runtime links and concepts to read next.

Five Graftcode integration scenarios: frontend to backend, backend to backend, backend to AI, polyglot in-memory runtime, and public API integration

  1. Frontend to backend — browser, desktop, or mobile Caller → Connect frontend to backend
  2. Backend to backend — service-to-service → Connect microservices
  3. Backend to AI — expose methods as MCP tools → Expose MCP for AI
  4. Polyglot in-memory runtime — multiple languages in one process → Switch between monolith and microservices · Use modules from any technology
  5. Public API integration — make a Receiver callable for others → Expose a backend service

Before production

Review current status and limitations, supported runtimes and package managers, authentication and authorization, and scaling.