Skip to main content
App developers, platform engineers, and recipe authors each follow different integration paths.
The user identifies their role below and opens the matching persona workflow.

Quick Start

1

Simple Usage

Ask the router which persona and path fits your work.
2

With Configuration

Add your language and environment for a targeted workflow.

How It Works


Persona 1: App Developer (Backend/Fullstack)

Role Description

Backend or fullstack developers who integrate AI capabilities into applications. They consume recipes created by others and focus on reliable integration.

Primary Goals

  • Integrate AI features quickly
  • Ensure reliability and error handling
  • Minimize infrastructure complexity
  • Meet performance requirements
  1. Model 1 (Embedded SDK) - For Python applications
  2. Model 3 (HTTP Sidecar) - For polyglot microservices
  3. Model 2 (CLI) - For scripts and automation

Typical Workflow

1

Discover Available Recipes

2

Test Recipe Locally

3

Integrate into Application

4

Add Error Handling

Key Concerns

  • Latency: Monitor recipe execution time
  • Error handling: Graceful degradation when recipes fail
  • Observability: Logging, metrics, tracing
  • Testing: Mock recipes in unit tests

Persona 2: Platform/DevOps Engineer

Role Description

Engineers responsible for deploying, scaling, and operating recipe infrastructure. They manage servers, authentication, monitoring, and security.

Primary Goals

  • Reliable recipe server deployment
  • Secure multi-tenant access
  • Monitoring and alerting
  • Cost optimization
  1. Model 4 (Remote Runner) - Production deployments
  2. Model 5 (Event-Driven) - High-scale async processing

Typical Workflow

1

Configure Server

2

Deploy with Docker

3

Set Up Monitoring

4

Configure Load Balancer

5

Set Up Alerts

Key Concerns

  • Security: API key rotation, TLS, network policies
  • Scaling: Horizontal scaling, load balancing
  • Availability: Health checks, failover
  • Cost: Resource utilization, API costs

Persona 3: Recipe Author / Solutions Engineer

Role Description

Engineers who create and maintain recipes. They design AI workflows, configure agents, and ensure recipes meet business requirements.

Primary Goals

  • Create reusable, reliable recipes
  • Document inputs/outputs clearly
  • Ensure security and compliance
  • Optimize for performance and cost
1

Initialize Recipe Project

2

Define Recipe Schema

3

Define Workflow

4

Validate Recipe

5

Test Recipe

6

Package and Distribute

Key Concerns

  • Schema design: Clear, well-documented inputs/outputs
  • Security: Tool restrictions, data handling policies
  • Testing: Comprehensive test cases
  • Versioning: Semantic versioning, changelog

Persona Collaboration

Best Practices

Recipe Authors set tools.allow and tools.deny in TEMPLATE.yaml so a recipe can only reach the capabilities it needs — deny shell.exec and file.write unless required.
praisonai recipe validate catches schema errors early. Run it in CI so broken recipes never reach App Developers.
App Developers should catch RecipeTimeoutError and RecipeError and fall back cleanly rather than surfacing raw errors to users.
Platform/DevOps can set preload: true in serve.yaml so the first request does not pay the recipe load cost.

Integration Models

Technical integration options per persona

Decision Guide

Choose the model that fits your role