Software R&D
& Prototyping
Compare technical approaches with a working prototype. Get test results, code, and a recommendation for what to build next.
The work
Find out before the full build.
Test feasibility
A feasibility study tests whether an approach can meet the constraints. Define the result that would change your decision.
Compare approaches
A proof of concept tests one technical assumption. Compare options against the same inputs and success criteria.
Build a prototype
A product prototype connects the workflow so people can try it. Record what works and what still needs testing.
From question to experiment
You have an idea whose feasibility is unclear, several possible technical approaches, or an experiment that needs better testing. The first task is to identify what you need to learn and which result would change your decision. Studies can also compare blockchain designs, TEE boundaries, zero-knowledge proofs, or FHE on a defined workload.
We agree on the assumptions, constraints, and success criteria. We then build the smallest experiment that can test the important questions, record the results, and explain their limits.
Published research / Illustrative workflow
A research question with a testable answer
- 01
The question
Could a PHP session path still reach the known destructor bug after the patch?
- 02
The experiment
Compare the named release builds in controlled labs, with instrumented runs and positive and negative controls.
- 03
The finding
The published tests reached a memory error and, in a separate configured lab, a fixed command. Each result required specific conditions.
- 04
The next decision
Test which application profiles expose those conditions and document the paths that stop the chain.
This is published research by the founder. It does not establish that a default PHP installation exposes the tested chain.
Read the exampleWhat you receive
Leave with evidence you can use.
Findings and technical recommendations.
Prototype code and setup instructions.
Test conditions, observations, and known limitations.
A proposed path to further development, revision, or stopping.
Selected work
Relevant research and engineering
Research by the founder · Published research
PHP after the patch
A research series examining PHP memory behavior, patch paths, and application conditions through source analysis and controlled reproductions.
Research & technical investigations
Experiments, source analysis, and engineering contributions across software, AI, and security.
Engineering by the founder
Ghostline
A Wi-Fi motion-tracking prototype. Andrei “Pax” Popa contributed board validation, diagnostics, and a React diagnostics app, as acknowledged in the preprint.
Read the preprintBefore we start
How does a feasibility study differ from a prototype?
A study answers a technical question. A proof of concept tests an assumption in code. A prototype connects enough of the product workflow for people to try it. We choose the smallest useful scope.
What if the experiment shows that the idea is unsuitable?
The findings should explain why, which constraints mattered, and whether another approach is worth testing.
Can the work continue into development?
Yes. Use the findings to agree the implementation scope, unresolved risks, and acceptance criteria before the next build.
Can a prototype continue into an MVP?
Yes. Use the findings to define a usable first release through Software & Product Development. Agree the core workflow, remaining risks, acceptance checks, and operating requirements before implementation.
Contact
Discuss a research project
Tell us your goal, context, and constraints. For a focused technical consultation, we agree the question, preparation, session scope, and written next steps before work begins.
Discuss your project