MaybeMake absence and failure explicit.

Option, Result, Schema and DTO for dependency-light PHP 7.4+ applications. Adopt one boundary at a time across Windows and legacy codebases.

Start in 5 minutes

See a real migration

MIT licensePHP ≥ 7.4CI passing Packagist

inputResultOkErr

composer require gabrielalmir/maybeInstall →

customer.php

use Maybe\Schema\Schema;

$result = Schema::shape([
    'email' => Schema::string()->trimmed(),
])->safeParse($payload)
    ->andThen(fn (array $data) => saveCustomer($data));

$result->match(
    fn (Customer $customer) => "Ok: saved",
    fn (mixed $error) => "Err: fix input"
);

Option

Model optional values without null checks scattered everywhere. Some/None with map, flatMap, filter and safe unwrapping.

Read Option

Result

Typed success/error flows without exceptions as control flow. Chain fallible operations with andThen and recover with orElse.

Read Result

Schema

Zod-inspired, immutable parsing and validation. Compose strings, ints, enums, arrays and object shapes with rich error reporting.

Read Schema

DTO

Validated object mapping from raw input. One schema, one immutable DTO — returns a Result instead of throwing.

Read DTO

Start at the boundary you already have

No framework coupling, no rewrite. Validate input, model a fallible service, and decide what happens at the edge.

Install the core primitives

composer require gabrielalmir/maybe

Read the first steps →

Use the boundary you have

Need isolated concurrency?Run serializable work in child processes with Async, including timeouts, pools and cancellation.Maintaining a CI3 application?Adopt helpers and explicit outcomes one controller at a time without a rewrite.

New here? Read Why Maybe? for the trade-offs, follow the Tutorial to build a validated flow end to end, or keep the API Reference open while you work.