Service Standards
Standards We Hold Ourselves To
Not marketing claims — operating rules that apply to every engagement, regardless of size.
Written scope before billing
No billable work begins without a written scope covering deliverables, assumptions, and exclusions.
Staging before production
Changes are built and validated on staging first. Production is never the first test environment.
Backup before structural change
A verified backup is taken before any upgrade, migration, or structural configuration change.
Checklist validation
Work is confirmed against a validation checklist, not marked complete on a visual glance.
Honest about limitations
We tell you when something can't be guaranteed (indexing, rankings, zero downtime) rather than implying it can.
No credential requests through public forms
We never ask for OJS admin, hosting, database, or SSH credentials through a public web form.
For formal response-time commitments, see our Service Level Agreement. For data-handling practices, see Data Security.