Developer partner path

Learn the platform and deliver production apps for your own customers.

This page is built for developers and implementation partners who want to build on Jetstack independently. It connects technical onboarding, API integration, and practical delivery opportunities.

Track 1

Implementers

Implementation guidance covers platform foundations, model design, views, canvas composition, and automation workflows.

  • Application modules and data model paradigm
  • Object types, object properties, and data views
  • Automations, trigger system, and workflows
  • Public pages and custom forms
Track 2

Integrators

The integration track focuses on REST API architecture, webhook patterns, and practical connectivity to external services.

  • REST API architecture overview
  • API-based interaction with model entities
  • Webhook-driven event handling
  • Service-to-service connectivity patterns

Suggested developer onboarding sequence

A practical path for teams that want to deliver customer-facing systems on Jetstack.

1

Understand the model

Build a pilot module with objects, permissions, and key views to internalize core patterns.

2

Add process logic

Introduce automations, button actions, and event hooks around real workflow states.

3

Integrate and ship

Connect external services via API/webhooks, validate UAT, and deploy with confidence.

Developer-oriented capabilities

Technical advantages that matter for long-term maintainability and delivery speed.

On-the-fly API reflection

Model changes are reflected in API behavior so integration layers can adapt quickly.

Hooks and internal API

Listen to system-level events and attach custom logic for deeper workflow control.

Custom widgets and plugins

Use built-in widgets and extend behavior through custom coding where needed.

Permissions-aware tooling

Role and access controls are part of core architecture, reducing authorization boilerplate.

Public pages with logic

Expose selected app areas externally while preserving data and permission boundaries.

Notification pathways

Deliver updates in-app, by e-mail, or via push notifications with custom relay options.

How to position Jetstack to your clients

When clients ask “why not just use AI app generation tools?”, these are the practical arguments implementation teams can use.

Prototype speed without production volatility

Prompt-first tools can accelerate concept creation, but production apps need deterministic behavior. Jetstack keeps changes intentional and reviewable.

No infrastructure operations burden

Your client does not need to own deployment and maintenance complexity just to keep the system healthy and scalable.

Clear mapping from user story to feature

Model, workflow, and UI adjustments are explicit and reproducible, which reduces ambiguity in scope and acceptance.

Better long-term delivery confidence

Teams can ship rapidly while preserving consistency and governance expected in serious business environments.

Want to become an implementation partner?

Share your team profile and target use cases to plan onboarding, delivery model, and cooperation setup.

Browse doc map