1. Scope of work
Digitalith Systems works within defined scope. Deliverables, dependencies, timelines, acceptance points, and exclusions should be documented before implementation begins.
Terms
Terms for scoped infrastructure deployment and support.
These terms clarify infrastructure review, deployment scope, support boundaries, third-party dependencies, client responsibilities, and change requests.
This page provides general business terms. Project-specific agreements, proposals, statements of work, and invoices may define additional or overriding terms.
2. Infrastructure review
A review or discussion does not create an obligation to deploy, support, or maintain any system until scope, pricing, access, and responsibilities are agreed.
3. Client responsibilities
Clients are responsible for providing accurate information, timely access, internal approvals, third-party account access where required, and decision-makers for acceptance.
4. Access and administrative control
Access requirements should be agreed before work begins. Client-managed systems remain client responsibility unless Digitalith is explicitly engaged to support them within scope.
5. Support boundaries
Support is scoped. Foundational support, deployment stabilization, or change support only applies where agreed. No unbounded maintenance or continuous operational coverage is implied.
6. Third-party dependencies
Hosting providers, registrars, payment processors, email providers, APIs, plugins, connectivity services, and other third parties may affect delivery or resolution timing. Digitalith is not responsible for third-party outages outside agreed scope.
7. Change requests
Changes outside approved scope may require separate review, pricing, timeline adjustment, or written approval before execution.
8. Unauthorized modifications
Client or third-party changes made outside agreed process may affect stability, warranty, troubleshooting, and support responsibility for impacted components.
9. Documentation and handover
Where included, Digitalith provides practical documentation, admin notes, or handover guidance to support maintainability after deployment.
10. Timelines and resolution
Delivery and resolution timing depend on scope, access, complexity, approvals, third-party dependencies, and operational conditions.
11. Intellectual property
Ownership of final deliverables, reusable components, third-party assets, licensed tools, and pre-existing materials should be defined in the relevant project agreement.
12. Limitation of claims
Digitalith does not claim ISO/SOC certification, large-scale managed operations, promised uptime, or continuous monitoring unless specifically stated in a signed agreement.
Scope clarity
Define deployment expectations before work begins.
Structured infrastructure work requires clear scope, access, responsibilities, support boundaries, and change control.
Contact
For project-specific terms, use the request page or email contact@digitalith.com.