Supporting digital foundations
Website Care & Maintenance
Keep ownership, changes, and website health visible within a written maintenance and support boundary.
Buyer problem
A launched website still needs an accountable owner.
Dependencies change, content becomes stale, providers have incidents, and edits can introduce regressions. Maintenance is useful when the systems, checks, change rights, and response path are explicit.
Jaly defines what is observed, what may be changed, who approves it, and what happens outside coverage. A public page cannot promise continuous security, uninterrupted availability, or a response window.
What the work can include
Defined deliverables, not an open-ended promise.
-
System and access inventory
Platform, hosting, domain, dependencies, repositories, providers, owners, and recovery access documented.
-
Change control
A defined request path, approval owner, test expectation, release record, and rollback approach for covered changes.
-
Health checks
The written scope may cover availability, dependencies, forms, backups, performance, or accessibility checks.
-
Issue triage and reporting
Observed issues, severity, ownership, decisions, and excluded work recorded without implying unlimited support.
Inputs and entry criteria
- Administrative access and proof of ownership
- A current backup or approved recovery approach
- A named change and approval owner
- A documented list of systems and support expectations
Limits and exclusions
- No guarantee of uptime, security, recovery time, or vulnerability prevention
- No implied around-the-clock monitoring or response window
- Third-party provider behavior remains outside Jaly control
- AI-system evaluation and operations require a separate scope
FAQ
Frequently Asked Questions
What can a website care engagement include?
Depending on the written scope, it can include dependency review, backups, availability checks, performance review, content changes, and issue triage.
Does a care plan guarantee uptime or security?
No. Monitoring and maintenance can reduce risk and improve response information, but they cannot eliminate outages, vulnerabilities, provider failures, or attacks.
Can Jaly support a site it did not build?
Sometimes. A technical review confirms platform access, code quality, hosting, dependencies, ownership, backup state, and which risks must be addressed first.
What counts as a content update?
The written scope defines the size, frequency, review requirements, and exclusions for content changes. New pages, redesigns, integrations, and features are normally separate work.
Is website care the same as managed AI operations?
No. Website care covers a public digital property. Managed AI operations covers evaluation, failures, source freshness, model or provider changes, usage, and controlled production changes for an AI-assisted system.