Update links (#742)

README.md

@@ -16,7 +16,7 @@
 Plane is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s mulitplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document.
 
 Use cases include:
-- Scaling up [authoritative multiplayer backends](https://driftingin.space/posts/you-might-not-need-a-crdt).
+- Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt).
 - Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes).
 - Data-intensive applications that need a dedicated high-RAM process for each active user session.
 

docs/pages/concepts/session-backends.mdx

@@ -25,4 +25,4 @@ Although the term *session backend* is relatively new, the concept is not. [Figm
 about their multiplayer approach which could be described as a session backend, as could the architecture
 of the [Jupyter](https://jupyter.org/) scientific computing environment and [VS Code for the web](https://code.visualstudio.com/docs/editor/vscode-web).
 
-Read more about [session backends](https://driftingin.space/posts/session-lived-application-backends).
+Read more about [session backends](https://jamsocket.com/blog/session-backends).

docs/pages/developing/contributing.mdx

@@ -1,7 +1,7 @@
 # Contributing to Plane
 
 Plane is [developed on GitHub](https://github.com/jamsocket/plane), primarily by the
-[Drifting in Space](https://driftingin.space/) team.
+[Jamsocket](https://jamsocket.com/) team.
 
 We accept code contributions, as long as they are aligned with our roadmap and vision for Plane.
 

docs/pages/index.mdx

@@ -16,7 +16,7 @@ import Logo from '../components/logo'
 Plane is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s multiplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document.
 
 Use cases include:
-- Scaling up [authoritative multiplayer backends](https://driftingin.space/posts/you-might-not-need-a-crdt).
+- Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt).
 - Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes).
 - Data-intensive applications that need a dedicated high-RAM process for each active user session.
 

docs/theme.config.jsx

@@ -12,7 +12,7 @@ export default {
     },
     footer: {
         text: <span>
-            Plane is an open-source project of <a href="https://driftingin.space">Drifting in Space Corp.</a>
+            Plane is an open-source project of <a href="https://jamsocket.com">Jamsocket.</a>
         </span>,
     },
     head: () => {

plane/README.md

@@ -11,7 +11,7 @@
 [Plane](https://plane.dev) is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s mulitplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document.
 
 Use cases include:
-- Scaling up [authoritative multiplayer backends](https://driftingin.space/posts/you-might-not-need-a-crdt).
+- Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt).
 - Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes).
 - Data-intensive applications that need a dedicated high-RAM process for each active user session.