Automotive service intelligence In development

Find the fault.
Verify the fix.

Tixengi brings vehicle symptoms, diagnostic evidence, inspections and repair history into one structured workflow — helping workshops and fleet teams investigate with context and document what actually fixed the problem.

Evidence before parts replacement.
Technician-led decisions, with clear records from intake to verification.

Automotive technician reviewing diagnostic information beside a vehicle in a workshop
WORKSHOP WORKSPACE Sample view
VEHICLE CASE · SAMPLE DATAToyota Camry · 2018
In diagnosis
P0171P01012 observations
Suggested next checkInspect intake system connections

Illustrative guidance only. Technician verification required.

01Vehicle context
02Diagnostic evidence
03Repair verification
04Reusable history
Technician connecting an OBD diagnostic scanner to a vehicle
A code is a clue — not a complete diagnosis.

The problem

The scanner shows what the vehicle reported. Not always why it happened.

Vehicle faults are investigated across disconnected tools, paper notes, chat threads, scan results and technician memory. That makes context hard to preserve and repeat repairs harder to prevent.

01

Evidence is scattered

Codes, customer complaints, photos and repair history rarely live in the same case.

02

Symptoms can have several causes

A fault code points an investigation in a direction; it does not prove which component failed.

03

Previous visits lose context

When findings are not captured consistently, the next technician may repeat checks.

04

Repairs need a clear close-out

Parts and labour can be recorded without a consistent post-repair verification trail.

The product

One connected record from first symptom to verified repair.

Tixengi is being developed as a technician-led workspace that connects diagnostic clues, inspection steps and vehicle history without pretending that AI can replace professional judgement.

01

Diagnostic evidence, connected

Bring fault codes, driver complaints, mileage, inspection notes and prior repairs into one vehicle case so technicians can investigate with context.

02

Structured inspection paths

Turn a suspected cause into a documented sequence of checks, findings and verification steps. Suggestions support technician judgement rather than replace it.

03

Repair verification

Record the work performed, the parts considered, the post-repair scan and the road-test outcome before a case is marked complete.

04

A usable vehicle timeline

Keep maintenance events, previous complaints, evidence and repair outcomes together so the next visit does not start from zero.

05

Maintenance follow-up

Organise service reminders and post-repair check-ins around mileage, service intervals and the work completed.

06

Fleet pattern review

Surface repeated repairs and similar symptoms across vehicles for a human reviewer to investigate before deciding what action to take.

Product preview

A workshop view built around the work — not another dashboard.

Explore an illustrative workspace with fictional cases. This is a front-end concept, not a live diagnostic system or production customer data.

SAMPLE DATA
WORKSPACE / OVERVIEW

Workshop overview

Demo environment
Open cases05 Across sample bays
Awaiting approval01Customer response needed
Needs verification02Complete close-out steps

Vehicle cases

Search or filter illustrative records

CASE / VEHICLEISSUESTATUS
TX-0184Toyota Camry · 2018Lean fuel trim · P0171In diagnosis
TX-0201Ford Transit · 2021Intermittent starting complaintAwaiting approval
TX-0207Toyota Hilux · 2020Front suspension noiseRepair in progress
TX-0212Honda Accord · 2019Post-repair verificationVerification
TX-0219Nissan Navara · 2022Scheduled maintenance dueScheduled

How it works

A repeatable process for every repair.

The workflow keeps evidence and decisions connected, from intake to final verification.

01

Capture the vehicle

Create a record with vehicle details, mileage and the customer’s reported symptoms.

02

Bring evidence together

Record fault codes, inspection notes, photos and relevant repair history.

03

Investigate with context

Use structured checks and AI-assisted suggestions to guide technician review.

04

Complete and verify

Document the repair, repeat checks and record the outcome before close-out.

05

Preserve what was learned

Add the visit to the vehicle timeline and organise the next maintenance follow-up.

Who it is for

Built around the people responsible for keeping vehicles moving.

Tixengi’s initial focus is B2B automotive service operations where repeatable records and verification matter.

Automotive service environment01

Independent workshops

Keep complaints, diagnostic evidence, work performed and close-out checks together across a busy service day.

Discuss your workflow
Automotive service environment02

Fleet maintenance teams

Review recurring issues across vehicles and preserve maintenance context between drivers, depots and service visits.

Discuss your workflow
Automotive service environment03

Mobile technicians & inspection centres

Capture findings consistently on site and hand over a traceable record of the inspection or repair.

Discuss your workflow

Proposed architecture

How We Use Amazon Web Services

Tixengi’s proposed AWS architecture is designed to handle vehicle records, supporting documents, workflow events and AI-assisted investigation. These services are architectural choices, not a claim that production infrastructure is already deployed.

Designed for technician review

AI output remains a suggestion. Vehicle-specific checks and repair decisions require qualified human judgement.

01

Collect

Vehicle details, symptoms, diagnostic results and inspection media.

Web app · API Gateway
02

Secure & store

Keep structured cases and supporting documents organised.

DynamoDB · S3
03

Process

Validate records and run workflow events and reminders.

Lambda · EventBridge
04

Assist

Generate evidence-linked summaries and suggested checks for review.

Amazon Bedrock
05

Review & act

Present the case history and next steps in the technician workspace.

React web app · Cognito

Amazon S3

Store uploaded inspection photos, service documents and supporting vehicle evidence.

Amazon Textract

Extract structured text from repair orders or service documents when document intake is implemented.

Amazon Bedrock

Support AI-assisted summarisation and evidence-linked investigation suggestions, subject to validation.

AWS Lambda

Run backend processing such as case updates, document handling and maintenance rules.

Amazon DynamoDB

Store structured vehicle cases, inspections, repair events and workflow state.

Amazon API Gateway

Expose authenticated application endpoints to the web client.

Amazon Cognito

Manage account authentication and access for workshops and teams.

Amazon EventBridge

Schedule maintenance reminders and follow-up events.

Amazon CloudWatch

Collect application logs and operational metrics for monitoring.

Proposed architecture. Final service selection depends on implementation, security review, workload requirements and operating cost.

Pricing

Simple plans, priced per location.

No per-vehicle fees and no per-case charges. Pick the plan that matches how many technicians work your bays.

Starter

For mobile technicians and small independent workshops.

$16

per location / month, $190 billed yearly

1 location · up to 3 technicians

  • Unlimited vehicle cases
  • Fault codes, symptoms and inspection notes in one record
  • Photo and document attachments (10 GB)
  • Repair verification checklist before close-out
  • Vehicle service timeline
  • Email support
Join early access

Fleet & multi-site

For fleet maintenance teams and groups with several sites.

Custom

Priced per site and fleet size

Multiple locations · unlimited technicians

  • Everything in Workshop
  • Fleet-wide repeat-repair and symptom pattern review
  • Depot and site-level reporting
  • Single sign-on and role-based access
  • API access and data import from existing systems
  • Dedicated onboarding
Talk to us
Founding-workshop offer

Join early access to use the Workshop plan free during the pilot, then keep 30% off any plan for your first year after launch.

Request early access

Planned launch prices in US dollars. Taxes may apply. Final pricing is confirmed before any paid plan begins.

FAQ

Questions workshops ask first.

Anything else? Email the founder directly and you will get a reply from a person.

Tixengi is in development. Early-access workshops help shape the product before general launch. Prices shown are the planned launch prices.

The Team Behind Tixengi

Better evidence. Clearer handovers.

Tixengi is being developed to help automotive service teams keep diagnostic reasoning and repair history connected.

Connect with the founder
AR
Founder

Abdulsalam Raji

Building Tixengi’s approach to vehicle diagnostics, repair workflow and maintenance intelligence.

LinkedIn profile
Tixengi mark

Early access

Help shape a more reliable repair workflow.

Tixengi is in development. If you run a workshop, manage a fleet or work in vehicle inspection, tell us where diagnostic and repair handovers break down.

No fabricated success state. Without a configured endpoint, this form opens a prefilled email.

Request early access

Share a little about your workflow.

By contacting Tixengi, you choose to send the details above by email. Please do not include sensitive vehicle-owner information.