# How it Works

At the heart of Saasmake is the simple idea that an app is a collection of connected services.

graph LR
    U[Client]
    U --> A[App]
    A --> S1[Service 1]
    A --> S2[Service 2]
    A --> S3[Service 3]

Services are things like Authentication and Billing, but also encompasses things like Blogs, Forums, and Landing Pages.

Anything a provider can create that has demand can be successfully packaged as a service.

# Flow

Requests arrive via your custom domain to your Saasmake App, which:

Performs ingress processing.
Routes the request to the relevant service.

The service then returns a response to your Saasmake app, which:

Performs egress processing.
Returns the response to the client.

sequenceDiagram
    Client->>App: Request
    App->>App: Ingress<br/>Processing
    App->>Service: [Request]
    Service->>App: Response
    App->>App: Egress<br/>Processing
    App->>Client: [Response]

# Configuration

You configure Saasmake through your dashboard, to define your:

Projects
Domains
Apps
Routes
Secrets

# Your App-as-a-Service

Within Saasmake your custom app logic is treated as a service.

This means Saasmake routes relevant requests to your custom app server just like it does for any other service.

graph LR
    U[User]
    U --> A[App]
    A --> S1[Service]
    A --> CP[Custom App]
    A --> S2[Service]

Implications:

You host your custom app logic wherever you like.
You configure which requests are routed to your custom app.
You can offer your custom app host as a service to others.