Collaboration

Scoped software.
Useful outcomes.

Japality Limited works with universities, research groups, and organisations on project-based AI systems, scientific software, data workflows, and product engineering. Each enquiry is reviewed for fit; work begins under a written agreement with clear deliverables.

01

AI systems

Agents, tooling & LLM workflows

Software that makes models useful in day-to-day development and research environments—agents, routing, evaluation loops, and workflow design. Public examples include BeanAlis, JapalityBean, and Japalitynil.

Typical project components

  • Terminal and CI coding-agent design
  • Model routing, evaluation, and verify gates
  • LLM workflow DSLs and orchestration
  • Tool use, MCP integrations, and guardrails
  • Retrieval pipelines and context packaging
  • Documentation, packaging, and handover
Note

Model outputs can be wrong. Validation, access control, and acceptable-use policy stay with the partner.

02

Scientific software

Data, methods & computational tools

Reproducible analysis, data workflows, visualisation, and domain-specific utilities—including sequence and NGS tooling when the project needs it. Our work is computational software and documentation.

Typical project components

  • Exploratory data analysis and review
  • Workflow automation and pipeline design
  • Sequence and NGS software utilities
  • Visualisation and data packaging
  • Reproducibility checks and method notes
  • CLI tools and file-format utilities
Data

Do not send sensitive datasets, credentials, or confidential files in an initial email. If a project proceeds, authority to use the data, transfer method, access, retention, and deletion are agreed in writing first.

03

Product engineering

Apps, utilities & maintainable delivery

From a compact research utility to a polished mobile product, we turn a well-defined technical process into software people can run repeatedly—including store-ready apps when that is the right distribution path.

Typical project components

  • Mobile and desktop prototypes
  • On-device processing where it helps
  • Developer tools and calculators
  • Workflow automation and file handling
  • Algorithm integration and performance work
  • Technical documentation and handover
Fit

Prototype and research software should match its stated purpose. Production, security, and quality expectations need to be written into the project scope when they matter.

Engagement model

What we clarify before work begins.

A written scope protects both sides and keeps delivery honest.

01

Purpose & users

Who the software is for, what success looks like, and what it must not be used for.

02

Inputs & access

Data types, ownership, permissions, and how materials will be shared.

03

Methods & validation

Documented approaches, known limits, and partner-side review where needed.

04

Security & retention

Transfer, access, processing location, minimisation, retention, and deletion.

05

Deliverables & IP

Outputs, documentation, ownership, licences, and reuse rights.

06

Commercial terms

Milestones, fees, timing, change control, and acceptance.

A useful first email includes

Enough context to assess fit

  • Your organisation and role
  • The problem in plain language
  • Whether it is AI, scientific software, data, or product work
  • The expected deliverable and timeline
  • Any hard constraints (platform, language, privacy, budget band)

Please hold off sending

Until terms are agreed

  • Large or sensitive datasets by email
  • Personal or health records
  • Production credentials or private keys
  • Third-party confidential material without clearance
  • Trade secrets in an unsolicited attachment

Project enquiry

Tell us the problem you want solved.

A short, non-confidential overview is enough to start a conversation. Collaboration depends on fit and a written agreement.

info@japality.com See our privacy notice for how we handle contact data.