Quick Start
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
Recommended Integration Models
- Model 1 (Embedded SDK) - For Python applications
- Model 3 (HTTP Sidecar) - For polyglot microservices
- Model 2 (CLI) - For scripts and automation
Typical Workflow
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
Recommended Integration Models
- Model 4 (Remote Runner) - Production deployments
- Model 5 (Event-Driven) - High-scale async processing
Typical Workflow
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
Recommended Workflow
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
Restrict tools in the recipe schema
Restrict tools in the recipe schema
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.Validate before you run
Validate before you run
praisonai recipe validate catches schema errors early. Run it in CI so broken recipes never reach App Developers.Handle recipe failures gracefully in apps
Handle recipe failures gracefully in apps
App Developers should catch
RecipeTimeoutError and RecipeError and fall back cleanly rather than surfacing raw errors to users.Preload recipes on the server for lower latency
Preload recipes on the server for lower latency
Platform/DevOps can set
preload: true in serve.yaml so the first request does not pay the recipe load cost.Related
Integration Models
Technical integration options per persona
Decision Guide
Choose the model that fits your role

