Project Info
Inspiration
In the medical AI space, clinicians and researchers often sit on high-value datasets but lack the tools and the time to turn them into actionable machine learning models. The current paradigm involves outsourcing to middlemen, which are ML engineers, who are far removed from the data collection and intent. Yet, even when the models are trained, they need to remain proprietary due to patient data privacy issues, which stop medical healthcare professionals from sharing their data, and enabling wide-spread sharing of their training pipeline. We wanted to flip that model: what if any medical professional could train and deploy state-of-the-art Vision Transformer (ViTs) models themselves, in minutes, no code required? What if, instead of sharing data, they could encode their hundreds of GB of data into low-level representation model adapters (LoRa adapters), which could be added for fast-shareable inference?
What it does
OKaiLoRa.ai is a no-code platform that simplifies healthcare model training, fine-tuning, and model sharing platform which allows medical professionals to: Upload image data for classification, segmentation, generation, or object detection, within our deployment server. Upload image data for classification, segmentation, generation, or object detection, within our deployment server. Select from a curated set of pre-trained models, which encompass the mainstream medical healthcare tasks, such as image classification, image segmentation, bounding box detection and generation. Select from a curated set of pre-trained models, which encompass the mainstream medical healthcare tasks, such as image classification, image segmentation, bounding box detection and generation. Train lightweight LoRa adapters on limited hardware (even with just 6GB VRAM)! Train lightweight LoRa adapters on limited hardware (even with just 6GB VRAM)! Track training metrics in real-time, no code, no setup! Track training metrics in real-time, no code, no setup! Share inference-ready models via secure Tailscale-powered links which point to the LoRa weight and fine-tuned weight checkpoints, keeping patient private data secure. Share inference-ready models via secure Tailscale-powered links which point to the LoRa weight and fine-tuned weight checkpoints, keeping patient private data secure.
How we built it
Frontend: Built in React, the UI supports drag-and-drop data uploads, dynamic sliders for model configuration, and real-time progress displays for accuracies, loss, and epoch. Backend: Powered by SpringBoot in Kotlin, we provide a robust REST API layer with the following key endpoints: /train/upload_data for zipped datasets. /train/start, /train/progress to manage and monitor training jobs. /inference/start, /inference/weights for remote model access. Training Engine: Uses PyTorch for clean training logic. LoRa adapters enable rapid fine-tuning with minimal GPU memory Hyperparameter tuning: Learning Rate Scheduler: Integrates the ScheduleFree optimizer, from the FAIR lab, which offers scheduler free learning rate optimizers for training pipeline (see NeurIPS 2025 paper: https://arxiv.org/pdf/2405.15682) Batch size is adapted automatically to fit the GPUs. Epoch number is customizable both by the user, or can be left at the default of 50 The classification pipeline supports any number of classes, determined through the files uploaded. Networking: Tailscale makes it easy to securely run inference from a shared link, ideal for labs or remote teams. Data Handling: Supports user-defined deployment_ids to track versions and LoRA adapter checkpoints for each model and dataset.
Accomplishments we're proud of
End-to-end drag-and-drop model training and inference with zero coding. Fully operational cross-stack integration (React ↔ Spring Boot ↔ PyTorch). Remote inference sharing via Tailscale and LoRA-based portability. Demonstrated rapid overfitting on small datasets to prove model training is functional and correct.
What we learned
Kotlin + Spring Boot provides a surprisingly clean and scalable backend for ML workflows. LoRa adapters are a game-changer for low-resource training and are so lightweight that we can use them to share fine-tuned models instead of full heavy ViT checkpoints!
What's next
for OKaiLoRa.ai We are currently hosted on our local servers, and would love to deploy to LoRa model hub: Upload and download LoRa weights like plugins for base models. Vision-language support: Let users describe tasks (e.g. “classify tumor types”) and auto-generate configurations. Research collaboration platform: Encourage ML researchers to submit healthcare models to our template zoo, following our standard.
OkaiLoRa
Inspiration
In the medical AI space, clinicians and researchers often sit on high-value datasets but lack the tools and the time to turn them into actionable machine learning models.
The current paradigm involves outsourcing to middlemen, which are ML engineers, who have no idea what the medical imaging data represents. Yet, even when the models are trained, they often need to remain proprietary due to data privacy issues, which stop medical healthcare professionals from sharing their data, and enabling wide-spread sharing of their training pipeline.
We wanted to flip that model: what if any medical professional could train and deploy state-of-the-art models themselves, in minutes, no code required? What if, instead of sharing data, they could encode their hundreds of GB of data into a low-level representations, which could be added to pretrained models for fast-shareable inference?
What it does
OKaiLoRa.ai is a no-code platform that simplifies healthcare model training, fine-tuning, and model sharing platform which allows medical professionals to:
-
Upload image data for classification, segmentation, generation, or object detection, within our deployment server.
-
Select from a curated set of pre-trained models, which encompass the mainstream medical healthcare tasks, such as image classification, image segmentation, bounding box detection and generation.
-
Train lightweight LoRa adapters on limited hardware (even with just 6GB VRAM)!
-
Track training metrics in real-time, no code, no setup!
-
Share inference-ready models via secure Tailscale-powered links which point to the LoRa weight and fine-tuned weight checkpoints, keeping patient private data secure.
How we built it
Frontend: Built in React, the UI supports drag-and-drop data uploads, dynamic sliders for model configuration, and real-time progress displays for accuracies, loss, and epoch.
Backend: Powered by SpringBoot in Kotlin, we provide a robust REST API layer with the following key endpoints: /train/upload_data for zipped datasets. /train/start, /train/progress to manage and monitor training jobs. /inference/start, /inference/weights for remote model access.
Training Engine: Uses PyTorch for clean training logic. LoRa adapters enable rapid fine-tuning with minimal GPU memory
Hyperparameter tuning:
- Learning Rate Scheduler: Integrates the ScheduleFree optimizer, from the FAIR lab, which offers scheduler free learning rate optimizers for training pipeline (see NeurIPS 2025 paper: https://arxiv.org/pdf/2405.15682)
- Batch size is adapted automatically to fit the GPUs.
- Epoch number is customizable both by the user, or can be left at the default of 50
- The classification pipeline supports any number of classes, determined through the files uploaded.
Networking: Tailscale makes it easy to securely run inference from a shared link, ideal for labs or remote teams.
Data Handling: Supports user-defined deployment_ids to track versions and LoRA adapter checkpoints for each model and dataset.
Accomplishments that we're proud of
End-to-end drag-and-drop model training and inference with zero coding.
Fully operational cross-stack integration (React ↔ Spring Boot ↔ PyTorch).
Remote inference sharing via Tailscale and LoRA-based portability.
Demonstrated rapid overfitting on small datasets to prove model training is functional and correct.
What we learned
Kotlin + Spring Boot provides a surprisingly clean and scalable backend for ML workflows.
LoRa adapters are a game-changer for low-resource training and are so lightweight that we can use them to share fine-tuned models instead of full heavy ViT checkpoints!
What's next for OKaiLoRa.ai
We are currently hosted on our local servers, and would love to deploy to LoRa model hub: Upload and download LoRa weights like plugins for base models.
Vision-language support: Let users describe tasks (e.g. “classify tumor types”) and auto-generate configurations.
Research collaboration platform: Encourage ML researchers to submit healthcare models to our template zoo, following our standard.
Analysis
View
Metric
- 61
- 22
- 15
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- KotlinIn code
- Next.jsIn code
- PythonIn code
- PyTorchIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
8 of 8 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
266 KB
Source files
73
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
xinlei55555/okailora
94 files · 732 KB · @ f78c2be
Structure
Interface
32 files · 34%Screens, components and styles rendered to the user.
Application logic
31 files · 33%Domain rules, services and shared utilities.
+4 moreData & schema
6 files · 6%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript77%
- Python10%
- Kotlin7%
- YAML4%
- Markdown2%
- Shell0%
- Other (1)0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
model_zoo/requirements.txt
pypi · 21- datasets
- einops
- loralib
- matplotlib
- numpy
- pandas
- peft
- Pillow
- pyarrow
- PyYAML
- Requests
- schedulefree
- scipy
- timm
- torch
- torchvision
- tqdm
- train
- +3 more
frontend/package.json
npm · 16- @types/uuid
- next
- react
- react-dom
- recharts
- uuid
- +10 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.