Skip to content
Let’s talk
INDROX / EXPLORE

INDROX / 03 / TechEvolution

Your software runs. Your business advances.

Monitoring and maintenance after delivery. Unlimited bug support, plus monthly hours for improvements.

Bugs do not use evolution hours.

IX · Indrox

01 / CONTINUITY AFTER DELIVERY

Monitor. Fix. Improve.

We care for your software after delivery to support your day-to-day operations.

Support continues when evolution hours run out.

Monitoring

We detect incidents in configured components and perform the agreed maintenance.

Corrective support

Diagnosis, fixes, testing and deployment for covered bugs, with no hourly limit.

Evolution

We plan your improvements and changes within the monthly allowance.

Support and evolution

A bug is covered functionality that does not meet the agreed behavior. Diagnosis, fixes, testing and deployment are included with no hourly limit: bugs do not consume your allowance or incur additional hourly charges.

Evolution means an improvement, modification or new behavior you request. Related analysis, development, testing, deployments and meetings consume that allowance.

02 / MONTHLY PLANS

Continuity that fits.

All: monitoring, agreed preventive maintenance, monthly report.

Active Evolution

Continuity and regular improvements.

US$599/month

Unlimited bug support

  • Prioritized backlog
  • Monthly improvement review
Evolution: 10 h/month
Ask about this plan: Active Evolution

Technology Partner

More evolution and technical guidance.

US$999/month

Unlimited bug support

  • Backlog and monthly review
  • Quarterly roadmap review
Evolution: 20 h/month
Ask about this plan: Technology Partner

Prices in USD, before applicable taxes. Allowances are totals per plan; they do not add up. No dedicated team or 24/7 human coverage, including Technology Partner.

03 / COMPARE COVERAGE

Compare the plans.

The same support foundation; different evolution capacity.

Allowances are totals per plan; they do not add up.
CoverageMonitoring + SupportActive EvolutionTechnology Partner
Covered bugsNo hourly limitNo hourly limitNo hourly limit
Monthly evolution4 hours10 hours20 hours
Maximum rollover to next month2 hours5 hours10 hours
Backlog and monthly reviewNot includedIncludedIncluded
Quarterly roadmap reviewNot includedNot includedIncluded

Terms and coverage

Additional hour: US$60, exclusively for evolution, with an estimate and prior written approval.

You can carry up to 50% of your allowance into the next month. That balance is used first and cannot roll over again.

We notify you when 80% of evolution hours have been used and report allowance usage.

For mixed requests, we separate bugs from evolution; we do not classify the entire ticket as evolution.

Initial diagnosis is not automatically charged when the cause turns out to be external or not a bug.

The allowance has a defined capacity: it is not unlimited development and does not mean every improvement will fit.

One subscription covers one inventoried and agreed product: its application, backend/API and associated panel. Technologies, versions and components are validated before activation; universal compatibility and automatic acceptance of third-party software are not offered.

Infrastructure, API usage, licenses, external services and app store fees are not included.

New products, modules or larger integrations are quoted separately. This does not allow a covered bug fix to be charged as an additional project.

Maintenance frequency, backups, restoration tests and the responsible parties are agreed per client. Daily backups and guaranteed recovery are not promised.

Mandatory changes from Apple, Google or other providers require an assessment of the agreed scope; they are not automatically classified as included or chargeable.

04 / HOURS & SLA

Support and response.

Mon–Fri, 9:00–18:00 · Lima (UTC−5). Excluding Peru’s national public holidays.

Automated monitoring does not mean 24/7 human support.

First human response within coverage hours; not a resolution deadline.
PriorityMonitoring + SupportActive EvolutionTechnology Partner
P1Total outage or critical flow with no workaround4 business hours2 business hours1 business hour
P2Significant partial failure8 business hours4 business hours4 business hours
P3Minor error with a workaround2 business days2 business days1 business day
P4Question or improvementAcknowledgment: 2 business daysAcknowledgment: 2 business daysAcknowledgment: 2 business days

Business day: 9 coverage hours. Outside these hours, the clock starts in the next window. P4: execution as planned. Coverage is formalized in the annex before activation.

Every detail, clear.

What does support cover?

A bug is covered functionality that does not meet the agreed behavior. Diagnosis, fixes, testing and deployment have no hourly limit and do not consume the allowance. Support continues when evolution hours run out. Mixed tickets are split into both types of work. Initial diagnosis is not automatically charged when the cause is external or not a bug.

How do evolution hours work?

They cover requested improvements, changes and new behavior: analysis, development, testing, deployments and meetings. This is not unlimited development. Additional hour: US$60, only with an estimate and prior written approval. Maximum rollover: 50% (Monitoring + Support: 2 hours; Active Evolution: 5 hours; Technology Partner: 10 hours); used first next month and never carried again. We notify you at 80% usage and report usage. Plan allowances do not add up.

When is support available, and what does the SLA guarantee?

Monday to Friday, 9:00–18:00, Lima (UTC−5), excluding Peru’s national public holidays. The SLA measures the first human response within coverage hours; outside them, the clock starts in the next window. It does not guarantee resolution or absolute availability. No plan includes 24/7 human on-call coverage or a dedicated team. Coverage is formalized before activation.

Which product and expenses does a subscription cover?

One inventoried product: application, backend/API and associated panel. Technologies, versions and components are validated; third-party software requires assessment. Infrastructure, API usage, licenses, external services and store fees are excluded. New products, modules or larger integrations are quoted separately, never a covered bug fix. Mandatory provider changes are assessed against the agreed scope without automatically classifying them as included or chargeable.

How are maintenance and backups agreed?

Frequency, backups, restoration tests and the responsible parties are agreed per client. Daily backups and guaranteed recovery are not promised.