Crozent
Services

Six practices that keep systems running

From the servers underneath to the interfaces on top — build, integrate, and maintain, with one team accountable for the result.

6
Service practices
33
Individual services
24/7
Maintenance cover available
100%
Client-owned infrastructure
01 — Servers

Servers

Compute, storage, and resilience sized to the workload — provisioned in your own cloud accounts and handed over with the controls.

Cloud Servers

Provisioned, sized, and hardened on AWS, Azure, or GCP, with autoscaling and cost controls in place from day one.

Storage Solutions

Object, block, and archival storage with lifecycle rules that keep growing data affordable.

GPU Cloud Servers

GPU instances for training, inference, and rendering, scheduled so idle capacity does not burn budget.

Multi-Cloud Managed Services

Workloads spread across providers with unified monitoring, access control, and billing visibility.

Disaster Recovery

Backup, replication, and tested failover plans with agreed RPO and RTO targets.

Development & Technology

Environment provisioning, tooling, and platform engineering so your developers ship without waiting on infrastructure.

02 — Web Development

Web Development

Sites and applications built to load fast, rank well, and stay editable by the people who own them.

Business Websites

Marketing sites that load fast, rank well, and are easy for your team to update without a developer.

E-Commerce Development

Storefronts with payments, inventory, and fulfilment wired into the systems you already run.

Web Applications

Browser-based tools for the work your business actually does, built to hold up under real load.

Custom Website Development

Bespoke builds for when a template cannot express your brand or your process.

CMS Development

WordPress, headless, or custom CMS setups your editors can use confidently.

UI / UX Design

Research, wireframes, and interface design that cut clicks and reduce support requests.

03 — API Development

API Development

Documented, versioned interfaces that other systems can depend on — with the operational detail that keeps them reliable.

REST API Development

Documented, versioned APIs with authentication, rate limiting, and predictable error handling.

Payment Gateway APIs

Razorpay, Stripe, PayU, and direct bank integrations with reconciliation and webhook handling.

Third-Party API Integration

Connect the services you already pay for, with retries and monitoring around every call.

Mobile App APIs

Backends built for mobile: small payloads, offline tolerance, and token-based authentication.

Enterprise APIs

Gateways, governance, and internal developer portals for organisations running many services.

04 — System Integration

System Integration

Make separate systems agree on the same data, so nobody re-keys information between screens.

Software Integration

Join applications that were never designed to talk, without manual re-keying in between.

ERP Integration

SAP, Oracle, Tally, and Dynamics connected to the systems around them.

CRM Integration

Salesforce, HubSpot, and Zoho kept in step with billing, support, and operations.

Payment System Integration

Payment rails wired into orders, invoicing, and reconciliation end to end.

Data Synchronization

Scheduled or real-time sync with explicit conflict rules, so no system silently drifts.

05 — Database Management

Database Management

Databases that stay fast, backed up, and secure as the data behind them grows.

MySQL Database Management

Provisioning, tuning, replication, and verified backups for MySQL and MariaDB.

PostgreSQL Administration

Performance tuning, extensions, version upgrades, and high-availability configuration.

MongoDB Management

Schema design, indexing, sharding, and cluster operations for document workloads.

SQL Server Management

Licensing-aware deployment, maintenance plans, and query tuning.

Database Optimization

Slow-query analysis, indexing strategy, and schema changes that cut response times.

Database Security

Access control, encryption at rest and in transit, auditing, and restore testing.

06 — Cloud Maintenance

Cloud Maintenance

The unglamorous work that keeps production boring: patched, watched, backed up, and quick to recover.

Cloud Monitoring

Metrics, logs, and alerts that tell you what broke and where, before customers notice.

Security Updates

Patching and dependency upgrades on a schedule, each with a rollback plan.

Performance Optimization

Find the real bottleneck, whether code, query, or infrastructure, and fix the one that matters.

Server Maintenance

Routine upkeep, capacity checks, and certificate renewals handled before they become incidents.

Backup Management

Automated backups with periodic restore tests, because an untested backup is not a backup.

Engagement models

Work with us the way that fits

Commercials are agreed before work starts. No open-ended meters.

Fixed-scope project

A defined outcome, timeline, and price. Best when the requirements are well understood.

  • Written scope and acceptance criteria
  • Milestone-based invoicing

Dedicated team

A ring-fenced squad working as an extension of yours, billed monthly.

  • Predictable monthly cost
  • Scales up or down with notice

Managed retainer

Ongoing maintenance, monitoring, and support against agreed response times.

  • Defined SLA by severity
  • Named escalation path
Managed support

Response targets by severity

Applies to clients on a maintenance or managed support agreement.

SeverityDefinitionResponse targetUpdate cadence
P1 — CriticalProduction down or data at risk1 hourHourly
P2 — HighMajor function impaired, no workaround4 business hoursTwice daily
P3 — MediumDegraded function with a workaround1 business dayDaily
P4 — LowMinor issue, question, or request3 business daysWeekly

TODO: confirm these response targets match the SLA you offer commercially.

Questions

Before you get in touch

How does an engagement usually start?

With a conversation, then a short discovery if the problem needs shape. Discovery produces an architecture outline, a scope you can hold us to, and a cost estimate.

Can you take over servers or code someone else built?

Yes. We start with an audit of what exists, then agree what is realistic to support, stabilise, or replace before committing to an SLA.

Who owns the infrastructure and code?

You do. Work happens in your cloud accounts and repositories wherever possible, documented so another team could pick it up.

Do you offer maintenance without having built the system?

Often, yes. Cloud maintenance and database management are commonly taken on for systems we did not originally build.

How is out-of-hours cover handled?

As a contracted option covering P1 and P2 incidents outside business hours, with an on-call rota and a named escalation path.

Not sure which service you need?

Describe the problem in a couple of sentences. We will tell you what we would do and roughly what it costs.