SLACredit
SLA financial credit governance for Jira Service Management
SLACredit turns service-level breaches into governed financial outcomes. It detects SLA breaches inside Jira Service Management, applies contract-specific credit and penalty rules, routes exemptions through structured waiver approvals, and locks each billing period under a SHA-256 verified snapshot so finance, delivery and clients reconcile against one immutable record.
- Runs on Atlassian
- Forge Zero-Egress
- Forge SQL & KVS storage
- SHA-256 period locking
₹ 1.2L exposure
- Open breaches
- 14
- Credit liability
- ₹ 2.9L
- Waivers queued
- 3
| Issue | Client | Breach | Credit | Status |
|---|---|---|---|---|
| MSP-4821 | Halcyon Logistics | 2h 14m | ₹ 48,000 | Credited |
| MSP-4796 | Northwind Retail | 38m | ₹ 6,500 | Waiver pending |
| MSP-4773 | Halcyon Logistics | 1h 02m | ₹ 12,000 | Exempted |
| MSP-4751 | Meridian Health | 6h 40m | ₹ 9,200 | Credited |
Capabilities
What SLACredit governs.
Designed for
- Managed service providers operating multi-client service desks
- Enterprise IT service desks with contractual service credits
- Finance and commercial teams reconciling SLA penalties and rebates
- Service delivery managers accountable for breach exemptions
Executive risk radar
A multi-tab governance workspace surfaces breach exposure, credit liability and waiver backlog by client, contract and period, so leadership sees financial risk before invoices go out.
Breach detection and credit engine
Automated SLA breach detection feeds a rule-driven calculation engine that converts each breach into a precise financial credit or penalty using the client contract in force.
Multi-client contracts and backtesting
Model each client contract with its own thresholds, caps and credit schedules, then backtest proposed terms against historical ticket data before committing them.
Exemption and waiver workflows
Structured breach exemptions move through multi-step approvals with justification, approver identity and timestamps recorded on every decision.
Cryptographic period locking
Close a billing period and SLACredit snapshots the ledger, computes a SHA-256 digest and verifies it on every subsequent read, making tampering detectable.
Audit-ready ledger exports
Export the financial and client rebate ledger with line-level provenance for finance systems, client statements and audit evidence.
Security architecture
Built natively on Atlassian Forge with zero external data egress
Trust & Security Center- 01All application compute executes on Atlassian Forge functions inside Atlassian Cloud.
- 02Contract, ledger and waiver data persist exclusively in Forge SQL and Forge Key-Value Storage within the customer tenant region.
- 03The application declares no external fetch permissions. No ticket, SLA or account data leaves Atlassian infrastructure.
- 04Access is governed by Atlassian product permissions and Jira project roles; SLACredit introduces no separate identity store.
- 05Period locks are verified with SHA-256 digests on read so that any divergence between stored and computed state is surfaced.
Commercial licensing
Tiered per-agent monthly commercial subscription.
Billed through Atlassian Marketplace Billing. Evaluation trial managed by Atlassian Marketplace.
Evaluation
Marketplace trial time-limited
Full functionality for evaluation on a non-production or pilot project.
- •All governance features
- •Marketplace-managed evaluation period
- •Standard support
Commercial subscription
Per agent per month, billed by Atlassian
Priced by Jira Service Management agent count on the Atlassian Marketplace listing.
- •Unlimited clients and contracts
- •Waiver workflows and backtesting
- •SHA-256 period locking
- •Ledger exports
- •Priority support
- Pricing, tier boundaries and invoicing are published and enforced on the Atlassian Marketplace listing.
- Invoices, taxes and refunds for Marketplace purchases are administered by Atlassian under the Atlassian Marketplace Terms of Use.
- Enterprise procurement questions are handled at billing@exobean.com.
Licensing terms are governed by the Commercial Software End User License Agreement and Terms of Service.
Privacy & data governance
What SLACredit processes, where it lives, and how it leaves.
The full annex is published in the Privacy Policy.
- Data processed
- Atlassian accountId of agents, approvers and requesters (opaque identifiers, no personal profile fields stored)
- Jira Service Management issue keys, SLA cycle timings and breach states
- Client contract parameters entered by administrators (thresholds, credit schedules, caps)
- Waiver justifications and approval decisions authored by administrators and approvers
- Storage
- Forge SQL and Forge Key-Value Storage provisioned for the installing Atlassian site.
- Residency
- Data residency follows the Atlassian Cloud region of the customer site; the application does not replicate data to any other location.
- Egress
- None. The application has no egress permissions and makes no calls to Exobean LLP infrastructure.
- Deletion
- Uninstalling the application triggers Atlassian-managed deletion of Forge storage. Administrators may request confirmation via privacy@exobean.com.
Frequently asked questions
More in the SLACredit documentation.
Does any of our Jira data leave Atlassian Cloud?
No. SLACredit runs entirely on Atlassian Forge with no egress permissions. Compute and storage stay within Atlassian Cloud in your site region.
How is a billing period locked?
An administrator closes the period. SLACredit snapshots the ledger, stores a SHA-256 digest and re-verifies that digest every time the period is read, so any change is detectable.
Can we model different terms for each client?
Yes. Each client contract carries its own thresholds, credit schedules, caps and exemption rules, and you can backtest proposed terms against historical tickets.
How is SLACredit licensed?
Through the Atlassian Marketplace as a per-agent monthly subscription with an evaluation trial. Atlassian handles invoicing and payment.