🛡️

Need support right now?

We're here to ensure every aspect of your Moroku platform — Money, Flow, Odyssey, and integrations — runs securely, reliably, and responsively. Log a ticket, send an email, or call us. Your SLA starts the moment you reach out.

Your SLAis activated the moment you contact us. We'll be on it.
Our Commitment

Your Success is Our Priority

We understand your success depends on our platform's reliability and our responsiveness to your needs.

📊

Proactive Monitoring

Continuous monitoring with Datadog and AWS CloudWatch detects issues before they impact you.

Rapid Response

24/7 alerting with automatic escalation ensures critical issues get immediate attention.

🔄

Continuous Improvement

Platform issues generate reusable IP that benefits all clients through shared improvements.

📋

Full Transparency

Real-time status page, incident post-mortems, and quarterly roadmap updates.

Cockpit ALPHA · GA OCT 2026

One window across your material service provider register.

Cockpit is the next release of Moroku's Services and Support offering. It consolidates the Jira service desk, the SLA framework, and Moroku's monitoring tooling into a single customer-facing console — and adds the observability surface banking customers need to satisfy their material service provider obligations under APRA CPS 230.

  • One console for tickets, SLA tracking, releases, security posture, and audit log — bank-controlled access via your own SSO.
  • Observe every material service provider on your CPS 230 register through connectors — core banking, payments, KYC, Open Banking, GL, document generation, and more.
  • Live SLA clocks on every ticket. Two-way Jira sync. RCA links on every Critical and High resolution.
  • Immutable audit log with seven-year retention, CSV and SIEM export, full filtering and search.
  • Bundled with standard SaaS for Moroku-source observability. Per-connector pricing for additional sources on the bank's register.
Service Level Agreement

Dual-Track Prioritisation

Joint Success Model: Issues that create reusable platform IP benefit all clients, while dedicated support handles your specific requirements. Reporting platform issues earns service credits and influences our product roadmap.

TRACK A

Platform Enhancement

Core functionality, security, performance, multi-client bugs, and feature enhancements.

SeverityResponseResolution
Critical2 hours4 hours
High4 hours12 hours
Medium24 hoursNext sprint
LowBi-weeklyQuarterly roadmap
TRACK B

Customer-Specific Support

Custom configurations, bespoke integrations, implementation support, and training.

TierResponseResolution
Premium4 hours48 hours
Standard24 hours5 business days
Premium clients receive 50% discount on all change requests and priority in bug-fix releases.
Support Packages

Choose Your Support Level

Enhance your support experience with our premium support options.

Standard Support
Included with all subscriptions
  • Dual-track SLA as outlined
  • Access to Jira support portal
  • Email and Slack support
  • Knowledge base access
  • Community forum access
  • Business hours support (9am – 5pm)
  • Bi-weekly release notes
Premium Support
50% faster response · 50% discount on changes
  • All Standard Support features
  • 50% reduction in response times
  • 50% discount on change requests
  • Priority in bug-fix releases
  • Extended hours (8am – 8pm)
  • Direct phone support
  • Monthly account review
  • Quarterly business reviews
How We Operate

Operational Excellence

Enterprise-grade processes ensure reliability, transparency, and continuous improvement.

📡

Proactive Monitoring

Continuous monitoring of CPU, memory, API latency, and third-party integrations. Automated recovery and engineer intervention before clients are affected.

🔍

Defect Triage & RCA

All incidents undergo structured triage with impact analysis, log review, and Root Cause Analysis. RCA summaries support transparency and regulatory governance.

🔄

Change Management

Agile release process with CI/CD pipelines and versioned deployments. All changes tagged to Jira, peer-reviewed with automated testing and rollback assurance.

🚀

Hypercare After Launch

6 weeks to 6 months of elevated support post go-live. Dedicated contact, faster SLA targets, fortnightly showcases, and direct Slack or video availability.

🎓

Training & Enablement

Role-specific training for Administrators, Customer Support, Credit & Ops Teams, Assessors, and Brokers. Includes manuals, webinars, and embedded help tools.

🎫

Incident Management

Structured workflow from identification to resolution. Incidents logged in Jira, categorised by severity, assigned with escalation paths, and retrospectives conducted.

🎫 Jira Service Management 💬 Slack Integration 📊 Datadog Monitoring ☁️ AWS CloudWatch 📈 Kanban Boards
Frequently Asked Questions

Common Questions

How do I log a support ticket?
Contact us via email (support@moroku.com), phone (+61 2 3815 0321), or the Jira Support Portal. All requests are logged, the 24/7 team notified via Slack, and your SLA activated immediately. When Cockpit ships, ticket creation will also be available directly inside the console alongside live SLA clocks and RCA links.
How are tickets prioritised?
We use a User Impact Score (UIS) methodology: (Affected Users × Severity Weight × Recency Factor) / Total User Base. Platform-wide issues receive appropriate priority even if reported by a single organisation.
What's the escalation process?
Duty Engineer identifies and assesses the issue, documents findings in Jira, and notifies stakeholders. If unresolved at first level, escalation to CTO for specialised expertise. Retrospective analysis prevents recurrence.
How will I be notified of outages?
Your primary operational contact is emailed for planned and unplanned outages. Critical incidents trigger notifications via status page and direct email to all affected clients. Cockpit will surface incidents in real time inside the console once GA.
What is Cockpit and when can I use it?
Cockpit is the next release of Moroku's Services and Support offering — a single customer-facing console that consolidates ticket management, SLA tracking, releases, security posture, and audit log. It also adds an observability surface for the third-party material service providers on your CPS 230 register. Cockpit is currently in alpha with general availability targeted for October 2026. Existing customers continue to use the Jira Support Portal until then.
What additional services are available?
Strategy consulting, software engineering, Agile coaching, Open Banking, core banking transformation, digital identity / KYC, experience design, CRM, digital marketing / SEO, board reporting, and vCTO / vCEO services.
Who are my key contacts?
Overall relationship and commercials: CEO. Technology, Product and Operations: CTO. Day-to-day requests should use the support channels above to expedite response by the operations team.