Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Internal Laravel Package

hyvor/internal

Internal Laravel/PHP package from Hyvor offering shared utilities and service integrations for Hyvor projects. Intended for internal application use, not as a general-purpose public library.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Email delivery infrastructure: The relay cloud feature in 4.1.10 enables Laravel applications to send transactional emails through Hyvor Relay’s cloud service, informing build-vs-buy decisions for email (self-hosted SMTP vs managed relay).
  • Feature roadmap for user notifications: Supports planning for password resets, onboarding sequences, receipts, and alerts without building custom email plumbing.
  • Reliability and deliverability strategy: Cloud relay can improve inbox placement and reduce operational burden versus maintaining in-house mail servers.
  • Vendor selection: Provides a Laravel-native integration path for teams already in the Hyvor ecosystem, affecting decisions on whether to standardize on Hyvor Relay or another provider.
  • Internal tooling and platform reuse: As an internal package, it signals reusable infrastructure for multiple Hyvor products; PMs can assess whether to expose similar capabilities to customers or keep them internal.

When to Consider This Package

  • Adopt when: You are building or maintaining a Laravel/PHP application that needs transactional email and you want a low-friction, first-party integration with Hyvor Relay cloud.
  • Adopt when: Your team values managed email delivery (deliverability, scaling, monitoring) over running SMTP infrastructure.
  • Adopt when: You are already using Hyvor services and want consistent tooling across products.
  • Look elsewhere when: You need marketing automation, advanced segmentation, or CRM-level email features beyond transactional relay.
  • Look elsewhere when: Your stack is not Laravel/PHP or you require a publicly documented, community-supported package with a broad ecosystem.
  • Look elsewhere when: You need multi-provider failover out of the box or deep integration with an existing email vendor (e.g., SendGrid, Postmark) that your team already operates.

How to Pitch It (Stakeholders)

For executives: This release adds a cloud relay capability that lets our Laravel apps send transactional email through Hyvor Relay without building or maintaining email infrastructure. It reduces operational risk, speeds up delivery of user-facing features (password resets, notifications), and supports a build-vs-buy decision that favors managed reliability over in-house SMTP.

For engineering: The package now includes a relay cloud feature (4.1.10), simplifying configuration for Hyvor Relay cloud email sending. It fits naturally into Laravel’s mail system, minimizes custom code, and centralizes delivery concerns. Evaluate it if we want a first-party path to managed email; avoid it if we need provider-agnostic abstraction or non-Laravel support.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
abbasudo/artisan-route
mirvan/ippanel
ignibyte/aic-framework
glavweb/data-schema-bundle
glavweb/datagrid-bundle
tacticmedia/scim-server
uni-method/frame
neika-ai/sdk
adachsoft/php-code-style
pharaonic/laravel-notification-dependencies
beautinow/translug
dev-brainiac/bot-cloaked
octoberrain/html
octoberrain/extension
octoberrain/exception
octoberrain/contracts
adachsoft/api-version-bundle
cgv/localized-resource
noith/settings
kda/laravel-package