KyperX AI

KyperX AI  /  Contact

Describe the workflow.

You do not need a defined AI project to start a useful conversation.

Prefer email? Contact us at ai@kyperx.com.

Enter your name

Enter your company

Enter a valid email address

Describe the workflow briefly

Please do not send confidential project documents with a first enquiry.

By submitting this form, you provide your information to KyperX Pty Limited so we can assess and respond to your enquiry. Form submissions are processed using Formspree, which is located in the United States. See our Privacy Policy. Prefer not to use the form? Email ai@kyperx.com.

Scope and terms

The questions worth asking before you engage anyone.

Including us. Vague answers to these are the main risk in an AI engagement.

Where is our data processed, and who can access it?

We identify where processing happens, which providers are involved, what access exists at each point, and whether a private deployment is available for your engagement. Local hosting reduces some exposures and does not eliminate risk — we will describe the actual data flows rather than make a blanket assurance.

What do we own at the end?

Custom deliverables built for you, your data, and the agreed rights to use them. Distinct from that are pre-existing KyperX components, third-party models and software under their own licences, and hosting infrastructure. The engagement states which is which, and the website will not promise ownership of things that are licensed.

Who runs it afterwards?

Either you or us. Handover is built so your team can operate the system, and we would rather that than create a dependency. Where you would prefer it run for you, ongoing operation and maintenance is available as a separate arrangement on its own terms — not bundled into the build.

How is cost assessed?

By comparing the relevant hardware, hosting, integration, maintenance and operating costs against your current baseline. We do not publish a savings percentage, because a figure without a defined scope and assumptions is not meaningful.

What happens if the pilot does not work?

It ends at the pilot. Acceptance criteria are agreed before the work starts, and a pilot that fails them is information rather than a commitment to continue. That is the reason for bounding the first engagement.

Which industries do you work in?

The services are industry-agnostic by design — what determines fit is the shape of the workflow, not the sector. If your work matches one of the shapes above, the approach applies. Describe it and we will tell you honestly whether it is a fit.