top of page
PLATFORM OPERATIONS

YOUR PLATFORM'S INFRASTRUCTURE, VISIBLE TO YOUR TEAM.

Cloud Monitor gives your team direct visibility into the AWS services behind your OneFin instance, pulled live from AWS CloudWatch. When something degrades, you see it on the dashboard instead of waiting to hear it from the support team.

onefin-cloud-monitor-wix.webp

THE PROBLEM

YOUR TEAM SHOULD NOT HAVE TO WAIT ON ANYONE TO SEE THE HEALTH OF THE PLATFORM

A lending platform running on managed AWS services depends on several layers working together: a database for loan records, container services for the application layer, a message queue for asynchronous jobs, a cache for performance, and a load balancer for traffic. Without direct visibility into these, an NBFC's own IT or operations team has one way to find out why disbursals, KYC checks, or repayment updates are running slow: raising a ticket and waiting for a diagnosis.

That gap matters most during an active incident. Every minute spent waiting on a vendor's response to "what's slow right now" is a minute the NBFC's own operations team cannot explain to a borrower, a branch, or their own management.

🎫
 TICKET-AND-WAIT DIAGNOSIS

Without direct access to infrastructure metrics, finding out why the platform is slow means opening a support ticket and waiting on the vendor for diagnosis.

📉
SILENT DEGRADATION

CPU exhaustion, memory pressure, or queue backlog can build for hours before it produces a customer-facing failure such as a stalled disbursal or a timed-out request.

🔍
NO INDEPENDENT ROOT CAUSE VIEW

When an incident is reported, the NBFC's team has no way to check which layer, database, queue, cache, or compute, is actually the cause, on their own.

📦
NO VISIBILITY FOR CAPACITY PLANNING

Storage headroom, burst credit consumption, and connection counts that would inform the NBFC's own scaling conversations with OneFin are not visible without asking for them.

WHAT ONEFIN MONITORS
FIVE AWS SERVICES. ONE DASHBOARD.

Cloud Monitor pulls data directly from AWS CloudWatch and the individual service APIs for every managed service the lending platform runs on.

🗄️

RDS

Database instance health and performance.

📦

ECS

Container service and task lifecycle state.

📨

RABBITMQ

Queue depth and message processing lag.

ELASTICACHE

Cache node load and hit rate.

🌐

LOAD BALANCER

Traffic volume and backend latency.

PLATFORM INTEGRATION

ACCESSED FROM WITHIN YOUR ONEFIN INSTANCE. SCOPED TO IT, TOO.

Cloud Monitor is exposed directly to clients rather than held back as an internal OneFin tool. Each client's dashboard is scoped to the AWS resources serving their own instance, not a shared view of OneFin's broader infrastructure.

🔗

PART OF THE PLATFORM YOUR TEAM ALREADY USES

No separate login or third-party monitoring tool to provision. Infrastructure health for the services behind your instance is available from the same platform your team uses for origination and servicing, and it shows only your resources.

HOW IT WORKS

DIRECT API CALLS. NO EXPORTS, NO MANUAL PULLS.

The dashboard reads live from AWS, rather than from a periodically exported
or replicated data set.

1
COLLECT REQUESTS

The dashboard issues requests for the metrics and metadata needed for each monitored AWS resource.

2
IAM ACCESS ROLE

Authentication runs through IAM Access Roles or access keys, scoped to CloudWatch and the relevant AWS service APIs.

3
DATA FROM CLOUDWATCH

Metric data is fetched directly from AWS CloudWatch and the individual service APIs for RDS, ECS, RabbitMQ, ElastiCache, and the load balancer.

4
RENDER VISUALS

Retrieved data is rendered into the dashboard's charts and status panels, visible to both OneFin's engineering team and the client's own IT or operations team.

KEY CAPABILITIES
METRIC COVERAGE ACROSS THE STACK.

🗄️

RDS INSTANCE MONITORING

DB identifier, status, engine type, VPC and subnet placement, storage type and size, Multi-AZ configuration, and endpoint details are visible without a console login, alongside compute load, available memory, disk headroom, and I/O throughput over time.

📦

ECS CLUSTER MONITORING

Per-service breakdown of running, pending, and desired task counts alongside CPU and memory utilization, so a stalled deployment or a resource-starved service is visible at the service level, not just the cluster level.

ELASTICACHE PERFORMANCE

Node-level compute load, available cache memory, cache hit rate, and active client connections are tracked per node, surfacing cache-layer strain before it appears as slower response times elsewhere in the stack.

📨

RABBITMQ QUEUE HEALTH

Messages waiting to be consumed, total active queues, and in-flight unacknowledged messages are tracked without opening the AWS Management Console, giving an early read on consumer lag before it backs up.

🌐

LOAD BALANCER TRAFFIC AND LATENCY

End-to-end latency from the load balancer to the backend target, where spikes signal downstream service degradation, alongside total request volume for correlating traffic load with performance changes.

OPERATIONAL OUTCOMES
WHAT CONTINUOUS VISIBILITY CHANGES.

🚀

FASTER MTTR

Issues surface within the dashboard rather than after navigating multiple AWS console pages, shortening the time between a metric spike and identifying its source.

🔎

PROACTIVE ALERTING

CPU exhaustion, memory pressure, and queue backlogs trigger configured alerts at defined thresholds, before they affect users - rather than being caught manually.

🔒

REDUCED CONSOLE DEPENDENCY

RDS, ECS, RabbitMQ, ElastiCache, and load balancer state are all visible in one dashboard, without logging into the AWS Management Console for routine checks.

📊

CAPACITY PLANNING

Historical trends across storage, memory, and I/O inform right-sizing decisions ahead of a capacity constraint, rather than in response to one.

WHO IT'S FOR
RELEVANT TO THE TEAM THAT HAS TO ANSWER FOR PLATFORM HEALTH.
CTO / IT

TECHNOLOGY LEADERS

Direct access to infrastructure health without waiting on a OneFin support response. Metrics for RDS, ECS, RabbitMQ, ElastiCache, and the load balancer are available the moment something looks slow.

COO / OPERATIONS

OPERATIONS LEADERS

When disbursal, KYC, or collections processing slows down, the cause can be checked directly instead of waiting on a ticket response before explaining the delay internally.

CRO / CFO

RISK AND FINANCE LEADERS

Infrastructure risk in a lending platform is business continuity risk. Direct visibility into the underlying AWS stack, rather than relying entirely on the vendor's word, supports the NBFC's own operational resilience posture.

SEE WHAT CLOUD MONITOR SHOWS FOR YOUR OWN INSTANCE.

We'll walk through the AWS services behind your OneFin deployment and the specific metrics tracked for each, including how your team would diagnose an incident directly.

bottom of page