- What is porto-sap/hello-api and what is it used for?
- It is the Composer name that publishes Apiato, an opinionated Laravel application skeleton built on the Porto SAP architecture, not a drop-in library. It provides a minimal REST endpoint plus pre-wired containers, OAuth2 auth, transformers, Docker setup, and exception handling. Use it as a starting point for greenfield API-centric backends and prototypes, not for bolting structure onto an existing app.
- How do I install porto-sap/hello-api in a Laravel app?
- You do not require it into an existing Laravel application; Apiato is consumed through composer create-project from the apiato/apiato repository. The skeleton brings its own app structure, container bootstrapping, route loading, auth, and test harness. Before adopting it, confirm the published artifact identity and pin a specific tag or commit.
- Is porto-sap/hello-api a Laravel package I can add with composer require?
- No, it is not designed as a standard drop-in library. Apiato replaces the app structure and bootstraps containers through its own service provider and kernel, and it owns exception handling, route loading, and testing. That explains why dependents are zero even though the project is popular: it is a create-project skeleton, not a dependency.
- What Laravel and PHP versions does Apiato support?
- The evaluation stack targets Laravel with PHP 8.2 or newer, but the exact support matrix should be confirmed with the maintainers. A recent 2025 release is positive but does not imply an LTS commitment. Pin Laravel and PHP versions explicitly in your architecture decision record and ask about upgrade cadence per Laravel major.
- Can I use Apiato in an existing Laravel application?
- Brownfield fit is low because Apiato assumes greenfield service design and enforces container boundaries that a typical Laravel monolith does not have. Third-party packages that expect the default App model namespace or standard PSR-4 autoloading will need bridging. For existing apps, extracting the Action, Task, Repository, and Transformer patterns is safer than a lift-and-shift.
- How does Apiato handle authentication and API responses?
- It pre-wires OAuth2 through Laravel Passport and uses Fractal transformers for API responses. That compresses platform scaffolding time, but both areas have moved on in the wider Laravel ecosystem toward Sanctum and API Resources. Expect to own those decisions rather than inherit them.
- How do I test an Apiato API project?
- Apiato ships a test harness, but the evaluation flags Codeception versus PHPUnit expectations as a diligence question. Container-aware configuration matters because migrations and seeders are relocated per Container. Ask the maintainers about typical suite runtime at scale before committing to the skeleton.
- Is Apiato production-ready and actively maintained?
- It has strong community interest but is effectively a single-maintainer project with community-only support. The dominant risk is governance rather than code quality. Resolve the name and repository mismatch, pin a commit, and confirm the security disclosure process and historical CVE turnaround before production use.
- What are alternatives to Apiato for building scalable Laravel APIs?
- Stock Laravel with Sanctum, API Resources, and a modular monolith structure is the lower-lock-in alternative. You can also extract the Action, Task, Repository, and Transformer conventions into a thin internal Composer package. That gives architectural uplift without adopting the whole opinionated skeleton. Apiato fits best when you want the full platform scaffold from day one.
- Does Apiato work with Laravel Octane, Swoole, or Docker?
- A Docker-based local environment is part of the standard setup. Octane and Swoole compatibility, including any stateful assumptions inside Containers, remains an open diligence question. Also verify observability SDKs and static analysis tooling such as PHPStan and Larastan with Container-aware configuration.