A colonnade where classical Roman arches meet Hindu-inspired pillar brackets.
Owned, not rented

Your A.I team, operating your systems.

Peristyle builds A.I team members and the private systems they need to operate — close to your data, your process, and your decisions.

Australian infrastructure Open-source software stack Self-hostable or managed Est. 2026
7
Free A.I Team Member + Software Templates
3
Privacy profiles, from entry to maximum
100%
Open Weights and Open Source
AU
Infrastructure, storage and inference by default
Four monumental stone pillars around a sunken courtyard.
The Team

A.I team members that run the systems, build the tools, and check the work.

Engineering, audit, and systems administration first — the work that has to be right before anything else is trusted. Each team member works a defined part of the business against your own data, using the same private system, and reports back to you — not to a vendor.

Software EngineerAuditorSys AdminSalesProcurementBookkeepingProject Manager

Swipe, scroll, or use the arrows — seven roles, one team.

A.I Team Member

Software Engineer

Builds and maintains the systems your business runs on — internal tools, integrations, and the pieces of software that would otherwise be bought from someone else.

Hands back Working internal tools, tested changes, integrations that keep talking to each other.
A.I Team Member

Auditor

Checks the work before it reaches you — reconciles the figures, tests the controls, and traces what was done back to what was meant to happen.

Hands back Reconciled numbers, tested controls, an audit trail you can hand over.
A.I Team Member

Sys Admin

Runs the infrastructure your people depend on — systems, access, and devices, with the onboarding, permissions, licences, and routine upkeep that stops a small chore becoming a weekend outage.

Hands back Access granted and revoked on time, systems kept patched, fewer surprises.
A.I Team Member

Sales

Works the pipeline: researches leads, qualifies enquiries, drafts follow-ups, and keeps your CRM honest so nothing quietly falls through.

Hands back Qualified leads, drafted outreach, weekly pipeline review.
A.I Team Member

Procurement

Sources suppliers, compares quotes, raises purchase orders, and tracks deliveries against the commitments that already matter to your operation.

Hands back Quote comparisons, draft orders, supplier follow-ups.
A.I Team Member

Bookkeeping

Categorises transactions, reconciles accounts, chases missing paperwork, and prepares the figures your accountant or bookkeeper actually wants to see.

Hands back Reconciled books, monthly reports, flagged exceptions.
A.I Team Member

Project Manager

Keeps the work moving — scopes what matters, sequences the steps, chases the dependencies, and tells you early when something is slipping.

Hands back A live schedule, chased blockers, no surprises at the deadline.
Beyond the roster

Custom Team Member + Software Systems on Request

If the work needs a role that is not on the list, we build the team member and the system it operates in around it.

Discuss a Custom Team Member
A terraced stone garden and stepped aqueduct merging into a workshop of instruments.

Systems for them to operate in

The A.I team members need somewhere to work. That somewhere is yours — data, process, and pace, kept under your own control.

What stays yours

The team only matters if the system stays yours.

The system they operate inside is the product. Everything else is plumbing that should never become somebody else's business.

01

The data

The team members work against sources you control, inside infrastructure you choose. Your working material is not feeding someone else's product.

02

The process

Prompts, retrieval, routing, thresholds, and approvals are tuned to the way your team already works — not a generic sequence from a vendor playbook.

03

The pace

You improve the system where the work happens. Refinements land on your own schedule, not a remote platform's release notes.

How we begin

Map the work. Place the team. Refine in use.

Step 01

Map the current process

We look at the handoffs, sources, review points, approvals, and exceptions that already define how the work moves.

Step 02

Place the team where they belong

The A.I team members and the systems they operate inside are deployed into the environment that matches your operating boundary and your preferences for control.

Step 03

Refine against real use

Once the work is live, we tighten prompts, retrieval, outputs, and decision rules until the team feels native to the process rather than bolted onto it.

An open stone threshold leading to a sunlit courtyard.
Start with the work

Bring a process you’d rather not do yourself.

Tell us where the data lives, how the work moves today, and what has to stay under your control. That is usually enough to start a serious conversation.

Start a Conversation