Frequently asked questions

Orping is ESS health monitoring for Oracle Fusion: a dashboard for job health, Slack-based notifications on failures, an intelligence layer that surfaces prior fixes, and plain-English translation of Oracle errors.

Orping watches your Fusion ESS scheduled processes on a health dashboard and sends Slack alerts when a job fails or misses its schedule — with plain-English context and prior-fix intelligence.

No. Orping only notifies your team in Slack. You fix the job in Oracle Fusion.

Connect Orping with your Fusion hostname and REST credentials. Orping auto-discovers every ESS job on your instance and watches them continuously — alerts land in Slack the moment something fails.

All Fusion modules that run ESS scheduled processes — including Financials (GL, AP, AR, close), Supply Chain (inventory, costing, orders), HCM (payroll, benefits), Projects, and any custom jobs your team runs in Fusion.

No. Orping focuses exclusively on Oracle Fusion ESS scheduled processes. We do not monitor Oracle Integration Cloud (OIC) or third-party integration runtimes.

Yes. Critical Fusion jobs often run with different ledgers, periods, business units, or submission parameters. Add each combination you care about; Orping polls them separately and alerts Slack when that specific run fails or is late.

Yes. Add any ESS job involved in period close, quarter-end, or financial close — including GL, AP, AR, FA, SCM costing, and custom processes. Your Slack channel gets the alert instead of discovering failures in the morning.

Orping.io is designed for Oracle Fusion Cloud (SaaS) ESS and scheduled processes accessed via the standard REST API. On-prem EBS batch monitoring is on our roadmap — join the waitlist to influence priority.

No OCI agent and no desktop install. Orping uses outbound HTTPS from our servers to your Fusion tenant. If your environment restricts API access by IP, add Orping's egress IP to your OCI allow list (we provide it at setup). Rarely, a corporate firewall may need to allow outbound HTTPS to your fa-*.oraclecloud.com hostname.

Whitelist Orping's egress IP in your OCI IP access policy (or equivalent Fusion restriction). No agent is required — email hello@orping.io during setup for the current IP. If connection still fails, check that outbound HTTPS to your Fusion hostname is allowed through your corporate firewall.

ESS job monitoring is included on all plans.

Standard ($399/mo after 14-day free trial): up to 25 seats · 5 channels · dashboard · plain English · one-click log · intelligence.

Enterprise: custom — Talk to sales.

Slack is your notification channel. Route by application or submitter with a granular rules engine.

Standard: 5 channels · Enterprise: multi-workspace

Standard: $399/mo after a 14-day free trial · up to 25 seats · 5 channels.

Enterprise: custom pricing.

Enterprise is custom — multi-Fusion-pod, OAuth 2.0/SSO, multi-workspace, dedicated support, and SLA.

Talk to sales for pricing.

Yes. Standard includes a 14-day free trial. Add to Slack to start — no credit card required to begin.

After 14 days, Standard is $399/mo.

Fusion teams who run ESS jobs and want ESS failures in Slack — Finance, SCM, HCM, and ERP admins.

Orping sends a Slack notification with the job name, status, and a plain-English explanation — routed by your rules engine on application or submitter to the right Slack channel.

Slack integration. Standard: 5 channels · Enterprise: multi-workspace

Alerts include job name, status, plain-English error details, and one-click resolution log.