Designed for structure.
Clear cues and repeatable workflows. No over-claims.
What is for sale right now
-
OracleBox Music Box (retail)
View Music BoxA standalone device built around a simple idea. When it triggers, you know it triggered.
It plays Twinkle, Twinkle, Little Star. The English lyrics were published in 1806. The melody dates back to the 1700s.
What it is testing for: motion in its detection field.
What can set it off: pets, people at the edge of range, HVAC airflow that moves curtains, heat sources, shifting sunlight or shadows, reflective surfaces, and anything that changes the scene.
How I validate it: let it settle, do a deliberate walk-through at known distances, then repeat the same walk-through and confirm the behavior matches.
-
OracleBox REM-Pod (retail)
View REM-PodA standalone proximity cue device built for clear, repeatable sessions.
What it is testing for: near-field or proximity-style changes and temperature trend context.
What can set it off: a hand or body approaching, conductive objects, static, moving cables, nearby electronics, and environmental temperature changes like HVAC cycles, sunlight, or body heat.
How I validate it: deliberate approach tests at controlled distance, confirm it settles, then repeat the same approach and confirm the behavior matches.
Custom requests (commissions)
Custom builds are for people who reach out and ask. Custom can mean a different color, a different enclosure, or a one-off device idea.
Tell me the workflow you are trying to run and the constraints you have. I will tell you what is realistic to build and support.
- Availability is not guaranteed
- Final features are listing and order-note specific
- Some custom builds can include a web page based control interface when requested
- Hub-based networking and WiFi features are not currently offered. If that changes, it will be stated on the listing.
How it is built
What OracleBox is
OracleBox is not a single device. It is a workflow plus a family of devices designed to support that workflow.
- A session should have a start, a stop, and a fixed set of settings
- An activation should be obvious and timestampable
- If you get a result, you should be able to try it again with the same setup
I am not interested in mystery behavior. I am interested in clear behavior that gives you something you can document.
How I design cues
A good cue is useful on camera and useful later when you review your notes.
- Obvious even if you are tired or distracted
- Shows up on video or audio so you do not rely on memory
- Consistent so you can compare one session to the next
That is why I favor clear feedback. A melody you can hear in the recording. A light cue you can see across the room. A repeatable trigger you can deliberately test.
How it works (high level)
This is the what and why, not the full blueprint.
- Observe something in the environment
- Stabilize and settle
- Detect change relative to baseline
- Show it clearly with an audio or visual cue
- Record context when it makes sense
In a real session you will usually notice a settling period, a clear state change, and a clean return toward baseline.
How I validate
I try to build devices you can sanity check without faith.
- Do a short baseline run in a quiet environment
- Trigger it on purpose in a controlled way
- Back off and confirm it settles
- Repeat the same approach at the same distance and compare behavior
If it does not behave consistently in a controlled test, it does not deserve to be interpreted in a session.
How I run a session
If you want the OracleBox way in one page, it is this.
- Write a goal in one sentence
- Document baseline conditions
- Pick a fixed segment length you can repeat
- Start recording
- Run the segment without changing multiple variables
- If something triggers, mark the moment and note environment changes
- Repeat with the same setup before interpreting anything
The point is to reduce the number of maybe explanations you are tempted to invent later.
OracleBox system
-
How to think about the system
Read the workflow guideOracleBox devices are built to give clear, repeatable cues you can document. Your method matters more than your gear.
- Run repeat sessions
- Change one variable at a time
- Use independent timestamps when possible
-
Retail lineup
Shop retail devicesRetail listings include the Music Box and the REM-Pod. Retail devices are standalone tools.
- Standalone Music Box trigger
- Standalone REM-Pod cue device
- No Wi-Fi or Bluetooth
- Support focused on setup
-
Personal system (not for sale)
ContactMy personal system is Hub-based. The Hub is used for internal testing and investigation workflows and is not a retail product.
- Hub doubles as a spirit box
- Used as a testbed for hub and satellite workflows
- Built around clear cues plus better session notes
- Have an idea for a custom build. Contact me and I will tell you if it is possible.
My personal system (not for sale)
I build personal devices that never show up as retail. This is the testbed where the OracleBox system becomes a living workflow.
- Hub plus satellites approach for internal testing
- A control interface to start and stop segments, mark moments, and keep a clean timeline
- Room labels so the timeline reads like a map
- Long-session friendly power options
These personal builds and prototypes are not retail products. Nothing in this section is a promise of a future retail feature unless it is stated on a listing.
Satellites
Not for sale. These are personal system builds and prototypes. If it is not listed in the shop, it is not being sold as retail.
When I say satellites, I mean the smaller devices I use around a space to create clean, timestampable moments. The goal is not mystery behavior. The goal is a cue you can test on purpose first, then recognize instantly on camera later.
In practice, that means the satellites are designed to do two things. Trigger clearly, and leave behind context that helps the timeline make sense when you review your notes.
REM-Pod style builds are built to be easy to sanity check. I do deliberate approach tests before any real run because normal factors like static, nearby electronics, moving cables, and distance changes can influence behavior.
Music Box variations follow the same philosophy as retail. Unmistakable cues. Some personal versions combine multiple cues to make the timeline easier to read, but that does not mean those features exist in retail.
Trip wires are hard markers. Something crossed a line. They are meant to be honest about normal causes too, like curtains, pets, and foot traffic, so you can label known triggers instead of guessing later.
The Matrix is a multi-cue approach I use when I want more than one point in the room. The point is cross-checking. One cue by itself is easy to overthink.
REM Halo is built for recording. If it activates, the camera catches it. That also means I am strict about validation and environmental control.
REM-Pod v2 is where I experiment with session modes and multi-sensor context so I can keep the method consistent and change one variable at a time.
Nothing in this section is a promise of a future retail feature unless it is stated on a listing.
Responsible claims
I do not claim OracleBox devices prove anything paranormal or guarantee outcomes. These are tools for controlled investigation and documentation-first workflows.
Questions
Does OracleBox prove the paranormal?
No.
Is OracleBox a single device?
No. It’s a system concept. Retail lineup is listed in the shop.
Do retail devices need internet?
No. Retail devices run standalone.
Can custom commissions include a control page?
Yes, sometimes. Custom commissions can include a web page based control interface when requested. Final features are listing and order-note specific.
Can I use these for security?
No.
Can I use my own recorder?
Yes.
Will you sell the Hub controller?
No. The Hub controller is not a retail product.
Do retail devices connect to each other?
No. Retail devices do not connect to each other.
Where do I start?
Start with one retail device based on your workflow. See the Shop page.
Are Trip wires, Matrix, REM Halo, and v2 devices for sale?
No. Those are personal system builds and prototypes. If it is not listed in the shop, it is not being sold as retail.