MARASA mark MARASA
0000-00-00 00:00:00 UTC
marasa

Silicon that evolves.

MARASA is building a chip that rearranges its own internals to run your code better. It keeps improving for years after deployment, with no human in the loop. It is built for the extremes. Extreme reliability in the orbit of Saturn. Extreme speed on the trading room floor.

fig. 1 / saturnrendered and dithered live, in your browser
what we are building

Hardware defined by the code it loads, not the silicon it launched with.

Most silicon is finished the day it leaves the fab. Ours is not. Load a program and the chip becomes that program. Leave it running and the chip keeps searching for a better way to be that program.

The search never touches what your code computes. Meaning is locked before the chip ever sees it, and every rearrangement is checked against that lock. What changes is how the computation sits in the hardware, and that is negotiable forever.

We call this software defined hardware. You write the code. The silicon takes it from there.

extreme / reliability

The orbit of Saturn.

A billion kilometers out, there are no repair crews. Radiation flips bits and wears down transistors until a fixed design fails. A MARASA chip treats damage as weather. It notices failing regions and moves the work somewhere else. The mission outlives the silicon it launched with.

extreme / speed

The trading room floor.

On the floor, a microsecond is a price. Strategies change weekly and the hardware under them takes months to respin. A MARASA chip retunes itself to the code it is running, so the silicon keeps pace with the strategy. No new tapeout. No hardware team in the critical path.

self-optimization, observed

The fabric, evolving.

Below is a sketch of the process. The chip tries new arrangements of the same computation and keeps the ones that measure better. When a region degrades it becomes expensive, and the layout drifts away from it. The result behaves exactly like the program you wrote, only faster, because that is the only thing it is allowed to become.

fig. 2 / placement under evolution gen 0000
the compiler

The compiler lives on the chip. It never finishes.

Its first output is a correct mapping of your program. Everything after that is improvement, measured on the actual hardware, under the actual workload. It is running today on our test systems. Ask to see it.

contact

Ready to get in early on the next big thing?

Reach out. We are quiet in public and specific in private.

fig. 3 / the other extreme
MARASA