Ryoss LabsBook a free discovery call

Insights

Ryoss publishes analysis, practical guidance and commentary on software, systems and technology decisions, with a focus on how those decisions affect organisations in practice. The writing is grounded in how organisations actually run systems, not a schedule of promotional posts.

Article

  1. Where AI should assist, but not own the judgement, in higher education

    AI can help with curriculum, course material, assessment, admissions and integrity work. The harder question is whether the institution can still explain, review and take responsibility for the judgement that affects a student's learning or outcome.

  2. When an integration platform is enough, and when custom integration is worth building

    Zapier and Power Automate can be the sensible way to connect systems when the workflow is clear and failure is easy to recover from. Custom integration becomes more attractive as state, reconciliation, throughput and operational consequences become harder to leave inside a platform abstraction.

  3. Where AI helps software development, and where engineering ownership still matters

    AI can make implementation, tests, documentation and security remediation cheaper to produce. Risk starts when generated software is trusted because it runs, while nobody still owns its architecture, security decisions or the ability to change it.

  4. When replacing ageing software is the wrong decision

    Replacing an ageing system can consume a year and still reproduce the same operational problems. This article looks at how to tell whether the problem is age, what the current system still holds, and what a replacement actually commits an organisation to.

Guide

  1. Where AI is useful in Australian higher education

    Higher education institutions can generate a long list of AI projects. The more useful question is whether someone can check the output, recover from a mistake, and keep the work grounded in information the institution already owns.

  2. What to establish before an integration project starts

    Before connecting two systems, an organisation needs to know which one owns the information, what should cause it to move, what happens when a transfer fails, and who is responsible once the integration is part of daily work.

Brief

  1. After 1 July 2026: AML/CTF in the systems firms already use

    From 1 July 2026, specified legal, accounting and real-estate services sit inside the Commonwealth AML/CTF regime. This brief looks at what that means for the systems those firms already use, and what they should now be able to see and record.

News

  1. What Ever Works is, and how it relates to Ever Gauzy

    Ever Gauzy is a business-management platform for ERP, CRM, HR and operational records. Ever Works is a separate agentic runtime for researching, generating and maintaining digital work. They sit in the same Ever Platform family and share some account and integration infrastructure, without a documented path for Works to operate on Gauzy's business records.

  2. When GitHub Actions is unavailable, what is actually blocked

    GitHub's 5 October Actions incident caused job failures and delays on hosted runners. For organisations that build and deploy through Actions, the useful question is what remains possible when the application is healthy but the release path is not.

  3. What Reflection's Beam announcement actually means

    Reflection has announced Beam, a sparse mixture-of-experts model with 501 billion total parameters and about 23 billion active for each token. The company positions it around inference efficiency. The public weights are still promised later in October.

  4. What Cloudflare's Web Search API changes for AI applications

    Cloudflare's Web Search API, launched on 2 October 2026 and still in open beta, puts Ceramic.ai, Exa and Linkup behind one interface and sends those searches through AI Gateway. An application can now choose, watch and replace the search provider without tying that decision to the model that reads the results.

  5. What the TPB's AI guidance means inside a tax or BAS practice

    When staff in a tax or BAS practice use AI, the TPB still holds the practitioner responsible for the work. This article looks at what a firm needs to know about the tools in use, the information they receive, and how generated output is reviewed.