Site Monitor
Check availability and expiry from your Capell application host.
- Version
- 1.1.4
- Released
- 10 November 2026
- Requires
- Discovery Foundation
- Licence
- Free
Price Free
Check access and installationCheck your application before checkout
What it solves
The problem
Our operators may miss an outage or an expiring certificate until visitors report it.
What your site gets
Our operators have availability and expiry records with incident history.
Questions buyers ask
- Where do monitoring checks run from?
- Checks run from the Capell application host, not an independent monitoring network.
- What must be running for alerts?
- Configure the scheduler, queue worker and notification integration before relying on alerts.
- Is Site Monitor a paid package?
- Site Monitor is a free first-party package.
Use it in your project
Configure a public URL, certificate or domain target, its interval and failure threshold. Keep the scheduler and queue worker running, then review check results and incident recovery in Capell admin. Connect incident events to your notification system; alerts are not delivered automatically. Use independent monitoring for outages that also stop this application host, and verify the exact package release before installing.
Picture it on your site
For a campaign launch, add the public campaign URL as a target and agree the interval, failure threshold and response owner. Run a check, inspect its result and confirm a failing target opens an incident that a later passing check resolves. Set up the scheduler, queue worker and incident-event notification integration before relying on the workflow. Certificate and domain-expiry targets support renewal planning. Keep independent monitoring for host outages, and confirm the exact released version includes the verified fixes before installing.
4 captures
Maintain and monitor your site
- Public URL availability, certificate and domain-expiry checks.
- Scoped target settings, run history and incident recovery.
Is this right for your project?
Make a signal actionable
An operational screen is most useful when a warning has an owner and a next step. Decide which checks matter to your site, who reviews them and how they distinguish an expected state from a failure. The package supplies its supported observations or controls; the application and hosting environment still determine the queues, schedules, credentials and infrastructure those checks depend on.
Exercise the recovery path
On a safe local or staging environment, follow one representative task from detection to resolution and confirm the public result afterwards. Check what happens when a dependency is unavailable and how the team knows the issue has cleared. Visible status is useful evidence, but it should sit alongside your deployment, monitoring and recovery procedures rather than replace them.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Add this free package to your account, then review compatibility and site impact before installing it.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens, command-line operations. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Uses package-local configuration and Capell metadata needed to enable the feature.
- Background work
- Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
- Access controls
- Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Require the package
composer require capell-app/site-monitor -
02
Install the extension
php artisan capell:extension-install capell-app/site-monitor
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.4 Nov 10, 2026
- Recent activity
- 13 approved releases in the last 12 months
Review evidence for this release
Free first-party availability and expiry monitoring with scoped target and incident resources, guarded outbound checks and verified scheduler, queue and incident recovery workflows.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.4
- Approval date
- Nov 8, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Checks run from the application host and require a working scheduler and adequately resourced queue worker. Keep independent monitoring for host outages. Incident events require a configured notification integration; email, SMS and on-call delivery are not automatic.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 13 approved releases-
v1.1.4Nov 10, 2026 -
v1.1.3Nov 2, 2026 -
v1.1.2Oct 28, 2026 -
v1.1.1Oct 20, 2026 -
v1.1.0Oct 17, 2026 -
v1.1.0-beta.45Oct 9, 2026 -
v1.1.0-beta.44Oct 8, 2026 -
v1.1.0-beta.43Oct 8, 2026 -
v1.1.0-beta.42Oct 7, 2026 -
v1.1.0-beta.41Oct 4, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.