Free audit · one database instance · mutual NDA before read-only access · no obligation
View Audit Scope
Scoped MySQL engineering projects
Fix slow queries, replication lag, upgrade risks, and availability gaps with a scoped engineering project. We agree the problem, deliverables, access, and validation plan with your team before work begins.
We review enquiries within 2–4 business hours (Mon–Fri 09:00–18:00 IST (UTC+5:30)). Contracted incident coverage follows the service agreement.
Bring a symptom, planned change, or architecture question. We will identify the next useful piece of work and whether it fits an audit, a consulting project, or ongoing DBA support.
No production credentials are needed to book a call. Diagnostic access is agreed separately.
Each option solves a different problem. The free audit is a small diagnostic review; consulting is a defined engineering project; Remote DBA is an ongoing service.
A read-only review of one instance and a prioritized report. Subject to engineer availability; the report is due within one week after the request is accepted and agreed access and inputs are ready. Implementation is outside the audit.
See the audit scopeA defined investigation, design, upgrade, migration, or remediation engagement. Your proposal sets the systems in scope, work products, schedule, and whether implementation is included.
Scope a projectRecurring database operations, monitoring, planned maintenance, and incident coverage. Hours and initial response targets depend on the service agreement.
Explore Remote DBAPublished client feedback
WeCredit shared this feedback about its database optimization engagement.
“They understood our requirements clearly, supported us with the right solutions, and helped us optimize our database in a very short time.”
Piyush Beli
CTO, WeCredit
When to bring in a MySQL consultant
A MySQL DBA consultant or database consultant investigates a defined performance, replication, or upgrade problem. We provide written findings and a plan your engineering leaders can approve and measure. For daily monitoring and maintenance, see our MySQL remote DBA service.
Your application slows down as traffic grows, but adding capacity has not fixed the cause.
Investigation: Trace expensive statements, wait events, indexes, and configuration against a workload baseline.
Useful output: A prioritized tuning plan with the expected impact and a way to measure each approved change.
Replica delays, uncertain failover, or a single database dependency put releases and recovery at risk.
Investigation: Review replication health, topology, failover paths, and backup restoration with your platform team.
Useful output: A target architecture, validation steps, and an operations runbook for the agreed scope.
A version change or cloud move has application compatibility and cutover risks you need to control.
Investigation: Assess dependencies, rehearse the move, define a cutover window, and prepare a rollback plan.
Useful output: A migration plan with explicit checks, owners, and go or no-go criteria.
Backups exist, but the team cannot yet show how quickly a failed database can be restored.
Investigation: Review backup coverage, point-in-time recovery, restoration steps, and operational handoffs.
Useful output: A recovery gap list and a test plan your team can run and repeat.
A consulting project starts with a written agreement on the result you need. Discovery, implementation, and ongoing coverage are separate decisions, so responsibilities are clear.
Tell us what is failing, what changed, and which systems matter. We agree the workload, success measures, and people involved.
The proposal defines deliverables, access, responsibilities, schedule, and acceptance criteria. An NDA can be signed before diagnostic access.
We start with approved, least-privilege access and share the evidence behind the diagnosis with your engineering team.
If implementation is in scope, your team approves production changes. We compare results with the baseline and hand over the agreed documentation.
Delivery timing starts from the agreed project schedule and depends on scope, approvals, and access readiness.
The exact work products are agreed in the statement of work. A typical performance or reliability project may include the following.
A record of the symptoms, workload measurements, likely causes, and the evidence used to rank them.
Recommended changes ordered by risk and impact, with dependencies, owners, and validation criteria.
Relevant configuration notes, migration or recovery steps, and a walkthrough for your team when included in the scope.
For a slow checkout query, the finding should show the query plan and workload evidence, explain why the current index is insufficient, describe the proposed change and its risk, and state how the team will compare latency and write cost before and after approval. This is an illustration of the report format, not a client result.
We choose diagnostics to fit the problem and platform. Your team can review the evidence before a change is proposed.
Slow query logs, execution plans, Performance Schema wait events, indexes, and storage behavior help locate where time is spent. Recommendations are checked against real workload patterns.
We review lag sources, replication configuration, topology, failover dependencies, and the path to restore service. A proposed design includes tests your team can repeat.
Version compatibility, application dependencies, data movement, cutover checks, and rollback planning are evaluated before the production window is approved.
We work with MySQL on Amazon RDS, Aurora MySQL, Google Cloud SQL, Azure Database for MySQL, and self-managed environments. Available diagnostics and change methods depend on the platform and agreed access.
We work alongside your engineering, infrastructure, and DevOps teams. Access and change controls are agreed for the project; your team approves production changes and retains the handover material.
JusDB engineering leadership
Raguraman, Engineering Manager · Allen D, Lead Database SRE
Agree confidentiality and the approved diagnostic surfaces before sharing credentials.
Start with the access needed to investigate. Changes require separate approval and appropriate permissions.
The proposal defines review meetings, documents, and the owners of follow-up work.
JusDB's security practices are aligned with ISO 27001 and SOC 2 Type II, and JusDB is pursuing both certifications (see Terms, section 12). Read the stated status.
Use the questions below to compare a defined consulting project with hiring internally, using a cloud provider, or buying ongoing support. Confirm actual scope and service levels in each proposal.
| Engagement model | When it fits | Typical scope | Confirm before you choose |
|---|---|---|---|
| JusDB MySQL consulting | A defined performance, reliability, upgrade, or architecture problem that needs specialist investigation. | Agreed project scope, written findings, and a prioritized plan. Implementation is included when agreed in the statement of work. | Objectives, deliverables, access, timeline, change approvals, and who owns the next steps. |
| Ongoing DBA service | Recurring MySQL monitoring, maintenance, and incident support. | Operational coverage and support defined by the provider agreement. | Coverage hours, escalation path, response targets, named owners, and exclusions. |
| Cloud-managed database | A managed platform for database infrastructure and routine platform operations. | Platform features and support covered by the selected cloud service and support plan. | Who owns query tuning, schema changes, upgrades, application issues, and incident coordination. |
| In-house MySQL team | Continuous ownership when MySQL work is closely tied to product and platform priorities. | Direct control over work and decisions, within the team's available time and expertise. | Capacity for specialist diagnosis, major changes, on-call coverage, and documentation. |
Coverage and deliverables depend on the agreement and your MySQL environment.
Answers about project scope, access, timelines, and how consulting differs from the free audit and ongoing support.
We start with a specific performance, replication, availability, upgrade, or migration problem. Before work begins, we agree the systems in scope, the access needed, deliverables, timeline, and approval points. A project may include diagnosis, written findings, a prioritized plan, and separately approved implementation and validation, depending on the agreed scope.
The free audit is an availability-dependent, read-only review of one database instance. It ends with a prioritized report within one week after agreed access and inputs are ready; production fixes are not included. Consulting is a separately scoped project for a specific problem or change. Ongoing DBA support is a separate retainer for continued operations and agreed response coverage.
Yes. Depending on the environment and agreed access, we can review slow query logs, execution plans, indexes, InnoDB and performance_schema metrics, and replication health. We establish a baseline, explain the likely causes, and propose changes with a way to validate their effect.
That depends on the current version, topology, application compatibility, and cutover options. We assess those risks, test the upgrade path, and agree a rollback plan and change window with your team. Some environments need a planned maintenance window; we do not guarantee zero downtime.
We can scope work on self-managed MySQL, AWS RDS for MySQL, Amazon Aurora MySQL, Google Cloud SQL for MySQL, Azure Database for MySQL Flexible Server, and Percona Server for MySQL. Available diagnostics and change methods vary by platform, so the proposal identifies the systems and permissions needed.
A scoping call needs no database credentials. For diagnostic work, we agree a mutual NDA and customer-approved, least-privilege read-only access to the systems and telemetry in scope. Production changes require separate approval, appropriate permissions, and an agreed validation and rollback plan.
We review enquiries within 2–4 business hours (Mon–Fri 09:00–18:00 IST (UTC+5:30)). A project start date and delivery schedule are confirmed after scope and engineer availability are agreed. Emergency coverage and initial-response targets apply only where they are included in a signed support agreement; a new consulting enquiry is not an emergency response service.
Tell us what is slow, fragile, or due to change. We will help define the investigation, the work products, and the approvals your team needs to move forward.
Need a different MySQL service? Browse our complete offerings.