Tired of building walls just to call your own code?
Skip the DTO, the endpoint, the postMessage bridge. Join JS peers and call across environments like ordinary code.
What this is
Fullstack work keeps paying a wall tax. Every time a domain idea crosses a process boundary, you invent a DTO, pick a REST-style endpoint or a postMessage vocabulary, and keep both sides in lockstep whenever the product moves. The call you meant becomes ceremony first.
Dewall is for that seam. After JavaScript peers join through a supported door, reading and calling feel like one environment — ordinary imports and local-looking calls. The transport mechanics stay under the hood; your attention can return to domain structure.
It is not a magic union of every backend on earth: JS peers, doors the library actually supports, and a public API still in beta. The promise is cognitive unity where the wall used to be the main job — not infinite reach.
Same wall, many guises
Boundaries fullstack teams already pay for. Each side stays in place — the ceremony is what gets replaced.
REST / DTO
Shape a wire type, pick an endpoint, keep client and server in lockstep whenever the domain moves.
Try a real topology
Worker↔worker, browser↔Node — pick a shape and see if the call feels local.
Prefer reading? Introduction · Getting started · Examples