URL: /baas/hybrid/introduction

---
title: "Hybrid Service Model"
description: "Combined CoreX and API approach for maximum flexibility"
---

# Hybrid Service Model

The Hybrid Service Model combines CoreX and API approaches for maximum flexibility.

## What is Hybrid?

Hybrid allows you to use CoreX for some processes while using API for others. This gives you the best of both worlds:

- **Speed**: Use CoreX for standard flows
- **Customization**: Use API for custom features
- **Flexibility**: Mix and match as needed

## Common Hybrid Patterns

| Use Case | CoreX | API |
|----------|-------|-----|
| **Standard + Custom Payments** | Onboarding, accounts | Custom payment UI |
| **White-Label + Custom Analytics** | Full front-end | Custom reporting |
| **Migration Path** | Start with CoreX | Gradually add API |

## Benefits

- **Faster Time to Market**: Launch with CoreX
- **Gradual Customization**: Add API integrations over time
- **Reduced Risk**: Proven CoreX + custom where needed
- **Cost Optimization**: CoreX for standard, API for differentiators

## When to Choose Hybrid

Choose Hybrid if you:

- Want to launch quickly but need some custom features
- Have limited initial resources but plan to customize later
- Need standard flows + specific differentiators
- Are migrating from CoreX to API gradually

## Admin Panel

Hybrid clients have unified access to the Admin Panel for both CoreX and API operations.

## Next Steps

<CardGroup cols={2}>
  <Card title="Getting Started" icon="rocket" href="/baas/hybrid/getting-started">
    Start with Hybrid
  </Card>
  <Card title="Configuration" icon="gear" href="/baas/hybrid/configuration">
    Configure Hybrid setup
  </Card>
</CardGroup>