Skip to content

Claude for your organisation. Hosted privately, in Australia.*

Diya is a private Claude assistant for your team's everyday work, built and run by Design Industries and hosted in Sydney.

A few things leave Australia when you use them, such as an optional model and web search. See the FAQ.

Start with the work on your desk.

Most requests are ordinary: a draft, a summary, a second look at the numbers. Diya is built for those first.

Write and summarise

Draft the email, the brief or the policy update. Attach up to five files and ask what matters.

Analyse

Hand over the numbers and get a chart or a worked answer. Calculations run in a sandbox with no network access.

Produce

Get a finished Word, PowerPoint, Excel or PDF file, or a live preview of a page or diagram.

A free account is chat, file attachments and projects on Claude Haiku. The analysis and document tools are switched on per person, for example in a pilot.

Hosted in Australia.*

Diya runs in Sydney. The standard Claude models (Opus, Sonnet and Haiku) run in Australian regions.

Stored and processed in Australia

  • Chats and prompts
  • Uploaded and generated files
  • Knowledge base, project sources and memories
  • Sign-in tokens for connected accounts, encrypted

What leaves Australia

A few things, such as an optional model, web search and the emails Diya sends. Each one is in the FAQ.

Who decides what

  • Administrators set each person's models, daily limits and access to the document and analysis tools, and which connections are on. On diya.au, those administrators are Design Industries'.
  • Project owners decide who can open each project, and are told if a Design Industries administrator adds themselves.
  • By default, Design Industries staff have no access to your chats in Diya.
  • Sign-ins and admin changes are logged.

Under the hood: AWS in Sydney, Claude through Amazon Bedrock, Cloudflare in front of the site. Your own cloud account is possible by arrangement.

Brief it once, not every time.

A project holds a team's instructions and sources. Every chat in it starts with that context.

Instructions
How your team wants things done, written once.
Sources
Up to 25 files or web pages. A project's sources stay private to the project.
Memories
Diya remembers what you tell it about how you work. You choose what applies to each project and can delete any of it.

Chats are private by default. Share one with a project's members when you want to.

It reads freely. It asks before it writes.

Connect Jira, Confluence, Slack, Google, SharePoint, Xero or HubSpot with your own account. Diya looks things up straight away. By default, anything that creates, changes or deletes waits for your approval. No answer in time means it is not done.

  • Jira and Confluence
  • Slack
  • Google Calendar
  • Google Drive
  • SharePoint
  • Xero
  • HubSpot

Administrators can add other systems through the open MCP standard.

Atlassian Solution Partner

More for teams on Jira and Confluence.

Design Industries is an Atlassian Solution Partner. Diya works in Jira and Confluence through Atlassian Rovo, as you, with your permissions. The optional Atlassian admin connection, arranged through Design Industries, adds a large set of tools for audits and configuration. Every change still waits for approval by default.

Do it once. Then let it run.

Turn a job you repeat into a workflow. Describe it and Diya drafts the steps, or start from a template. Run it from chat by typing /, or put it on a schedule.

A person at the gate

Any step can need approval, on screen or by email. On a schedule, the approver gets an email and the run waits up to 20 minutes. A change the AI tries on its own in a scheduled run is declined, unless the workflow's owner approved its changes in advance.

A record of each run

What each step did and produced, and a way to run it again.

From your own systems

Start and track runs through the API, with a personal key an administrator allows.

Common questions.

Short answers. The privacy policy has the detail.

Does everything stay in Australia?

Not everything. Your chats, files, projects and memories are stored and processed in Australia. A few things leave Australia when you use them:

  • Claude Fable 5, an optional model a person chooses, may be processed outside Australia, and its traffic is kept for up to 30 days for abuse checks. Auto never picks it unless they add it.
  • Web search and page reading use overseas services. So does adding a web page as a project source.
  • Emails Diya sends, such as sign-in codes and approval requests, go through Google Workspace.
  • Systems you connect, such as Jira, Slack and Google, receive what Diya sends them and keep it under their own terms.

Every visit to diya.au also passes through Cloudflare, and these pages load Google's sign-in code and fonts. The privacy policy lists each case.

Which Claude models can we use?

Claude Opus, Sonnet and Haiku, which run in Australian regions, and Claude Fable 5 as an opt-in model. Administrators choose the models each person can use, and Auto picks one of them for each message.

Who can see my chats?

You. A chat stays private until you share it with a project's members.

Design Industries runs Diya, and by default our staff have no access to your chats in Diya. One of our administrators can add themselves to a team project as a manager, for example to help its owner. The project's owner and managers are told straight away, and the administrator then sees what the project's managers see, including the chats its members have shared. Otherwise, we look at a chat only if you ask us to, to investigate a security problem or misuse of Diya, or when the law requires it. If we do, we tell you afterwards, unless the law stops us, or telling you would put someone at risk or undermine an investigation that is still going.

Our engineers keep Diya's servers running and can technically reach the data stored there. The same rules apply to them. Until we finish removing it, our application logs hold some text from chats, which engineers may read to fix faults. The privacy policy has the detail.

Does Diya change things in Jira or Confluence without asking?

Not by default. Diya looks things up straight away, but anything that creates, changes or deletes, in Jira, Confluence or any other connection, waits for your approval. In a chat, no answer within five minutes means it is not done. A workflow's owner can approve its changes in advance.

How do people sign in?

With a Google account, or with a one-time code sent to their email address.

Two ways to start.

Design Industries runs its own delivery, licensing and sales work on Diya.

Try it now

Start a guest chat, or sign in for a free account: Claude Haiku, 100 messages a day, projects, file attachments and your own connections.

Run a pilot

Design Industries sets up your team with the full Claude models, the document and analysis tools, and limits for each person.

Pilots are by arrangement.

Tell us what you want it to do.

A short note is enough: the work your team repeats, the tools you use, and roughly how many people. Someone from Design Industries will reply.

Goes to enquiry@di.net.au. See our privacy policy.