01
Odoo Learning Partner
Official partner credentials across Community and Enterprise delivery.
Operations · Retainers
Maintenance & Support
Long-term care for Odoo, Python, React, Node, servers, and databases — with clear SLAs, a 30-day bug fix window on our delivered work, and preventive methodology.
Credentials & trust
Proof before promises
We show the delivery record upfront: partner credentials, published case studies, and NDA-friendly engineering work you can review before sending an inquiry.
02
Odoo 10–19 expertise
Community & Enterprise Editions implementations, migrations, integrations, and custom modules.
03
45+ modules shipped
Custom modules across client projects, integrations, migrations, and partner work.
04
6+ years software development experience
Software delivery across employment, freelance consulting, and founder-led projects.
05
NDA & white-label ready
Partner-friendly delivery where client names and confidential work stay protected.
06
7 published case studies
Migrations, Shopify, POS, manufacturing, logistics, and self-hosted deployments.
Why choose us
Why choose our maintenance
Maintenance is the operating discipline that keeps Odoo, websites, apps, and servers trustworthy after go-live. For Odoo-specific AMC depth, see Odoo Support & Maintenance — this page explains the broader practice and why businesses retain Khichdi InfoTech.
Long-term partnership
The same engineers who understand your stack stay accountable — not a rotating L1 inbox that relearns your system every ticket.
Preventive maintenance
We schedule hygiene work so silent failures (jobs, disks, certificates, slow queries) are caught before users feel them.
Stable production systems
Change control, staging verification, and clear severity rules reduce “fix it live and hope” culture.
Faster issue resolution
Documented environments and named owners shorten triage. SLA timings define acknowledgement expectations.
Reduced downtime
Monitoring checkpoints, backup verification, and rollback awareness when risky changes are required.
Better system performance
Slow queries, heavy jobs, and application hotspots are treated as maintenance work — not ignored until a crisis.
Continuous improvements
Recurring tickets become backlog items: small hardening steps that compound into a calmer system.
What we maintain · Software
Applications and product surfaces
Odoo-heavy retainers may start on the Odoo Support flagship; this page covers the full stack.
Odoo
Bugs, configuration, upgrades, and performance for Community/Enterprise. Deep AMC methodology: Odoo Support.
Learn more →Python
APIs, workers, scripts, and service dependencies — including backends we ship or inherit.
Learn more →React
UI regressions, build/tooling updates, and client-side error patterns on production apps.
Learn more →Node.js
BFF/API services, process managers, and integration endpoints that must stay healthy.
Learn more →Custom applications
Internal tools and product surfaces that do not fit a single framework label but still need owners.
What we maintain · Infrastructure
Servers, databases, source & security
The layers under the app — where silent failures usually start.
Servers
Linux servers
OS patching coordination, disk/CPU signals, user access hygiene, and service restart discipline.
Web servers & reverse proxies
Nginx/Caddy (or equivalent) config, upstream health, and TLS termination checks.
Deployment configuration
Environment variables, release process, containers/compose, and “how we ship” documentation.
SSL & certificates
Renewal monitoring and replacement before expiry becomes an outage.
Scheduled jobs
Cron/systemd timers and application schedulers reviewed for failures and overlap.
Databases
PostgreSQL care
Connectivity, basic health, and coordination on growth issues that threaten uptime.
Performance optimization
Identify slow queries and indexing opportunities when symptoms appear in production.
Backup verification
Confirm backups exist and are restorable in principle — not only that a job “ran.”
Health monitoring
Disk, connections, and failure patterns that precede application-visible incidents.
Source code
Dependency updates
Controlled library and runtime updates with staging verification before production.
Code quality improvements
Targeted cleanups where technical debt causes recurring bugs or slow delivery.
Refactoring (scoped)
Small, safe refactors tied to risk reduction — not open-ended rewrites inside a retainer.
Technical debt reduction
Track debt explicitly; burn it down with agreed monthly capacity rather than ignoring it.
Security
Security patches
Apply relevant OS/app/framework notices in controlled windows.
Dependency vulnerability response
Prioritise high-impact CVEs affecting internet-facing surfaces first.
Access review
Periodic check that admin and deploy credentials still match the people who should have them.
Security best practices
Secrets out of repos, HTTPS everywhere practical, and least-privilege service accounts.
Performance
Slow queries
Find and fix database hotspots that create user-visible lag.
Server optimization
Worker counts, memory pressure, and capacity signals before blind hardware upgrades.
Application tuning
Heavy endpoints, N+1 patterns, and inefficient jobs addressed with measured changes.
Background jobs
Queue depth, failure retries, and job overlap that silently burns CPU or double-posts work.
Maintenance methodology
Onboarding through continuous optimization
A complete lifecycle — not a mailbox with a price tag.
- 01
Onboarding
Access, contacts, critical workflows, and channel agreement.
- 02
Environment review
Map staging/production, deploy path, backups, and monitoring gaps.
- 03
Health assessment
Baseline risks: certificates, failed jobs, error rates, disk, and known debt.
- 04
Preventive improvements
Schedule the highest-leverage hygiene items into the retainer capacity.
- 05
Monitoring
Watch the signals that matter for your stack; escalate when thresholds breach.
- 06
Monthly review
Tickets, themes, hours used, and recommended next actions — written, not vague.
- 07
Continuous optimization
Turn recurring incidents into permanent fixes so the system gets calmer over time.
Bug resolution policy
Complimentary fix window for our delivered work
For projects developed by Khichdi InfoTech, implementation bugs reported within 30 days after project delivery are fixed at no additional cost when caused by our delivered implementation. New features and scope changes are handled separately. After the complimentary window, maintenance plans cover ongoing assistance, monitoring, enhancements, and technical support.
- Applies to implementation bugs in work we delivered
- Must be reported within 30 days after project delivery
- Fixed at no additional cost during that window
- New features / scope changes are quoted or planned separately
- After 30 days, retainers provide ongoing support under SLA plans
SLA explanation
Response commitments
Response time is acknowledgement and triage start — not always a permanent fix in the same window. Chat often moves faster when an engineer is online; email remains the audit trail.
Essential
Small teams with occasional support needs
- Email support: within 8 hours
- WhatsApp / Telegram / Slack: 4–5 hours (or immediately when available)
- Bug fixes & minor updates
- Monthly health check
- Backup verification
Professional
Growing businesses that depend on Odoo daily
- Priority support
- Email support: within 3 hours
- WhatsApp / Telegram / Slack: within 2 hours (or immediately when available)
- Included change hours each month
- Odoo version upgrade planning
- Proactive monitoring checkpoints
Enterprise
Mission-critical systems with SLA requirements
- Immediate acknowledgement whenever possible
- Critical issue response: within 1–2 hours
- Email support: within 2 hours
- WhatsApp / Telegram / Slack: within 1 hour (or immediately when available)
- Named support engineer where contracted
- Quarterly review & roadmap
Pricing depends on environment size and scope. Contact for a tailored quote →
Quality assurance
How maintenance changes stay safe
Fixes are verified — and communicated — so production does not become a lab.
Regression testing after fixes
Re-check related flows so a hotfix does not reopen yesterday’s incident.
Verification before deployment
Prefer staging confirmation for non-emergency changes.
Change documentation
What changed, why, and how to verify — written for the next engineer (or your team).
Rollback planning
When a change is risky, we discuss rollback before deploy — not after a failed release.
Communication throughout
Status updates with owner and next checkpoint, especially on critical severity tickets.
Knowledge transfer & exit
Stay operable if you change partners
Documentation, credential ownership, and handover discipline are part of maintenance — not extras.
- Document recurring fixes and runbooks for your internal team
- Keep credentials and infrastructure ownership in your accounts
- Provide a structured handover package if you end the retainer
- Separate break/fix support from enhancement backlogs so capacity stays honest
System down or need urgent help?
We prioritise active retainer clients, then new support inquiries.
Long-term support
Delivery does not end at go-live
30-day complimentary bug fixes
Implementation bugs in our delivered work, reported within 30 days, are fixed at no additional cost. Features and scope changes are separate.
Maintenance retainers
After the complimentary window, SLA plans cover incidents, monitoring, and controlled enhancements.
Preventive care
Hygiene work reduces recurring fires — certificates, jobs, dependencies, and performance hotspots.
Exit without lock-in
You keep repos, credentials, and documentation if you change partners later.
Delivery process
A shared lifecycle across projects
- 01
Discovery
Constraints, systems, urgency, and success criteria.
- 02
Requirement analysis
Scope boundaries, risks, and acceptance criteria.
- 03
Solution planning
Approach, milestones, and staging/production path.
- 04
Development
Incremental delivery with reviewable changes.
- 05
Code review
Correctness, security, and maintainability checks.
- 06
Testing
Critical paths and regressions verified on staging.
- 07
Deployment
Controlled release with rollback awareness.
- 08
Knowledge transfer
Docs, runbooks, and admin enablement.
- 09
Complimentary support
30-day implementation bug-fix window on our delivered work.
- 10
Ongoing maintenance
Optional retainer for monitoring, incidents, and evolution.
Why trust this engagement
Signals that matter for this service
Relevant proof only — full credentials and portfolio remain available site-wide.
30-day complimentary bug fixes
On our delivered implementation work.
Approved SLA timings
Essential / Professional / Enterprise response windows.
Full-stack care
Odoo, Python, React, Node, servers, databases.
Exit without lock-in
Credentials and docs stay with you.
Related reading in the Knowledge Hub
Published guides, tools, and comparisons — no manual URL required.
Next step
Need Odoo-deep AMC methodology?
This page covers broader stacks. Odoo Support is the ERP-branded authority page.
Frequently asked questions
What are the response times?
Essential: email within 8 hours; WhatsApp/Telegram/Slack 4–5 hours (or immediately when available). Professional: priority queue; email within 3 hours; chat within 2 hours (or immediately when available). Enterprise: immediate acknowledgement whenever possible; critical issues within 1–2 hours; email within 2 hours; chat within 1 hour (or immediately when available).
Do you offer emergency / after-hours support?
Critical issues are prioritised within your plan’s support hours. Extended or 24/7 coverage is available only when explicitly contracted (typically Enterprise).
Can you maintain third-party or inherited codebases?
Yes, after an access and risk baseline. Opaque or unstable systems may need an assessment — and Odoo environments in crisis may belong on Odoo Rescue before a standard retainer.
What server access do you need?
Least-privilege access to the systems in scope: app/admin, repository, hosting panel or SSH, and database as required. Credentials should stay in accounts you own.
Are version upgrades included?
Upgrade planning and compatibility review can sit inside retainers. Large version jumps are usually scoped separately so incident capacity is not consumed silently.
How do bug fixes work after project delivery?
Implementation bugs in our delivered work, reported within 30 days, are fixed at no additional cost. After that window — or for inherited systems — maintenance plans apply. Features and scope changes are always separate.
Who owns the code and infrastructure?
You do. We work in your repositories and environments. We do not lock you into hosting or tooling you cannot leave.
Which support channels are used?
Email for formal tickets and audit trail; WhatsApp, Telegram, or Slack when included in the plan. The primary channel is agreed at onboarding.
How is this different from Odoo Support?
Odoo Support is the Odoo-branded authority page for ERP AMC. Maintenance is the broader page across Odoo, web, apps, servers, and databases. Odoo-heavy clients often start on Odoo Support.
Can you work on existing code or third-party projects?
Yes. We baseline access, risks, and documentation gaps first. Unstable systems may need assessment (or Odoo Rescue) before a standard retainer or dedicated seat.
How are urgent issues handled?
Severity rules decide interrupt priority. Support plans define acknowledgement windows; Enterprise includes faster critical response. True emergencies need access and a clear business impact statement.
What happens after delivery?
Knowledge transfer, then a 30-day complimentary window for implementation bugs in our delivered work. Ongoing care moves to a maintenance or Odoo Support retainer if you want continuous coverage.
Who owns the source code?
You do. Deliverables land in repositories and environments you control. We do not lock work behind proprietary hosting you cannot leave.
After you contact us
What happens next
Clear expectations reduce buying uncertainty — no mystery black box after you hit submit.
- 01
We review your inquiry
Within one business day we confirm understanding, ask for missing access/context, and propose the right engagement type.
- 02
We recommend a path
Project, dedicated capacity, support retainer, or rescue assessment — matched to your constraint, not a generic package.
- 03
You decide next
Scoped next step, commercial terms, and kickoff checklist. No hostage tooling — your repos and credentials stay yours.
Get a maintenance plan
Share stacks in scope and whether you need Essential, Professional, or Enterprise response timings.
