REFACTR.

Gpu-native infrastructure for serious compute

— Vision

The pipeline

should never be

the bottleneck.

Simulation, medical imaging, game development, scientific visualization: all share one constraint. The formats underneath them were not built for the data volumes they now handle.

The problem is not compute. Modern GPUs have headroom most pipelines never reach. The bottleneck is I/O: how geometry is stored, loaded, and moved through the stack.

Refactr builds the infrastructure layer that removes it. Format design, pipeline architecture, and GPU-native processing engineered so every stack built on top runs at the speed the hardware was always capable of.

— Recognition

Regional
Selectee

Zindigi Prize 2024

Among the top 60 teams regionally

Out of hundreds of teams competing across campus rounds, the team advanced to the Regional stage of the Zindigi Prize, evaluated on technical depth, market potential, and execution readiness.

Innovation Program · Pakistan · 2024

— Team

Built by people who ship,

not theorize.

Rameel Malik

CEO & Founder

Seven years at the intersection of graphics and systems. Built a real-time DICOM-to-3D lung visualization pipeline from scratch on a consumer GPU. When the tools he needed didn't exist, he built them. Founded Refactr to turn that instinct into infrastructure.

LinkedIn Email

Maryam

CPO & Co-Founder

Built the first half of Refactr's medical pipeline: preprocessing CT scans, segmenting lung tissue, and reconstructing 3D volumes from DICOM data. Unglamorous, load-bearing work that everything else sits on. That foundation shapes how initiates and chairs development. Zero to shipped.

LinkedIn Email

Dur Haider

CTO & Co-Founder

Thinks in hardware, builds in software. FPGA background gave him a rare instinct for where compute gets wasted and how to recover it. Migrated the entire pipeline to CUDA: 73% faster volume generation, 60% faster texture processing. If there's a faster path, he'll find it.

LinkedIn Email

— Technology

Performance is not a feature.

It is the foundation.

Zero parsing overhead

geometry loads directly into GPU memory

Pipeline Acceleration

Processing bottlenecks are I/O problems, not compute ones. We rebuild pipelines around GPU memory architecture, eliminating the CPU-bound parsing overhead that stalls serious workloads.

5× faster reads

vs STL · the standard in medical & simulation pipelines · validated on 10M+ vertex meshes · lossless

Proprietary Binary Format

Legacy formats store geometry as human-readable text, parsed character by character on every load. Our format is binary, compressed, and reads directly into memory with no parsing step.

10M+ vertices

processed in under 500ms on a consumer GPU

GPU-Accelerated Processing

Raw volumetric data to fully processed output, entirely on the GPU. Normals, compression, and format conversion run in parallel on the same hardware your renderer already uses.

— Format Benchmark

Numbers that speak

for themselves.

Format	File Size	Read Speed	Write Speed
Renex	570 MB	878 ms	2.17 s
OBJ	2.5 GB	1282 s	101 s
STL	1.4 GB	4.5 s	30 s
PLY	727 MB	30 s	10 s

Tested on a 14.5M vertex mesh. Median of 3 runs.

— Pipeline Runtimes

End-to-End Execution

At Scale.

Legacy Pipeline

OBJ + CPU

baseline

Our Format

Proprietary Format + CPU

1.7× faster

Our Format

Proprietary Format + GPU

6× faster

— Use Cases

Built for pipelines that

can't afford to wait.

Medical Imaging

Surgeons navigate millimetre-scale lung structures through flat 2D slices, where misreads are structural, not exceptional. 3D reconstruction changes surgical outcomes. Refactr built the proof of concept: a full pipeline from raw CT scan data to real-time 3D lung visualization with tumour localisation, running on a consumer GPU.

Game Development

Asset pipelines at scale spend more time moving geometry than rendering it. OBJ files that take minutes to load, format conversions that block the build, normals dropped on export. The I/O layer should never be the reason a pipeline stalls.

VFX and Film Production

Mesh data in VFX routinely exceeds tens of millions of polygons per asset. Read and write overhead at that scale compounds across every iteration. Faster I/O means more iterations in the same window, which is where quality actually comes from.

Work that ships.

We're building for rendering engineers, technical artists, and compute teams at studios and simulation labs who've already maxed out what their current pipeline can do.

Email us