skyphusion-labs / open source
Not for sale. Free use forever, developed entirely in the open. Product focus is Vivijure (self-hosted AI film studio: Cloudflare or your machine, dual-panel parity) and Postern (mailbox for humans and agents, identity-bound). Also Prism (public BYOK playground), The Hollow Grid, and AGPL tooling. Punk DIY bar with an aviation-grade finish. No account walls. Your GPU, your keys, your data.
Flagship
A self-hosted AI film studio you own: Studio 1.0 on an open host train with dual-panel parity. Run the control panel on Cloudflare (vivijure-cf) or on a home computer / any cloud server (vivijure-local); both share vivijure-core and ship studio features in the same release wave. Thin module host: storyboard, cast (SDXL + working Wan dual-expert LoRAs), render orchestration, agent MCP, finish chain. Rent GPU time on RunPod, run motion on your own card (LTX 12GB or CogVideoX 16GB), call cloud i2v per shot, assemble on CPU containers you host. Meet it at vivijure.com or try the live demo.
Not locked to Cloudflare. vivijure-cf runs on Workers; vivijure-local runs on a home PC or any cloud server. Same features, same wave (dual-panel parity). Shared orchestration in vivijure-core; agents drive either host with vivijure-mcp (cast, storyboard, uploads, library, artifacts).
github.com/skyphusion-labs/vivijureRunPod serverless GPU engine: SDXL cast LoRAs and keyframes, Wan image-to-video (with dual-expert Wan cast adapters from wan-train), quality tiers, finish helpers, ffmpeg assembly. Models baked offline; the release gate renders a real film before it promotes an image.
github.com/skyphusion-labs/vivijure-backendThe writers' room in Discord. Co-write a story, keep a structured storyboard, and ship to vivijure-cf or vivijure-local. Session memory and a traffic ledger keep cast, brief, and recent studio work searchable mid-conversation.
github.com/skyphusion-labs/slateCloudflare Workers control panel: planner, cast, render UI, JSON API, D1/R2, module workers. Builds on vivijure-core.
View repo →Same control panel on a home PC or any cloud server: Node, SQLite, S3/MinIO, Docker. No Cloudflare account required.
View repo →Shared orchestration both control panels consume: module registry, film pipeline, Platform ICD.
View repo →Drive the studio API from Claude, Cursor, or any MCP client: cast, storyboard, uploads, render library, artifacts. Works with both hosts.
View repo →Optional multi-tenant provisioner: accounts and one full studio per tenant from the published studio release. You never need this to self-host; same AGPL.
View repo →Speed door: LTX-Video image-to-video on a single 12GB consumer card. No cloud rent, reached over a tunnel.
View repo →Fidelity door: CogVideoX-5B image-to-video on a proven 16GB consumer GPU (production-ready).
View repo →Working satellite: Wan 2.2 A14B dual-expert character LoRA training for cloud image-to-video. Studio harvests high/low noise keys; render applies them at i2v time.
View repo →MuseTalk lip-sync on RunPod: face clip + audio track, mouth that matches the words.
View repo →Real-ESRGAN video upscale on GPU: 2x or 4x, streamed frames, NVENC encode, wall-clock bounded.
View repo →Speech cleanup before lip-sync: denoise, restore, stretch to 44.1 kHz so thin auto-generated voices come out natural.
View repo →Five always-on Docker services in vivijure-cf/containers (also used by the self-hosted host). On Cloudflare they are reached over Workers VPC; the host presigns object-store URLs and the containers stay stateless and credential-free. GPU money goes to diffusion; concat, mux, captions, portrait prep, beat sync, and loudness work run on CPU.
Concat per-shot clips, mux the audio bed, burn captions, title cards, and credits. The off-GPU tail of the pipeline.
View docs →Background removal for cast portraits before keyframe generation. Sharper cutouts, cleaner LoRA conditioning.
View docs →Beat-aware cutting when a film carries a music bed: shot boundaries land on musical beats, not arbitrary seconds.
View docs →Film-level audio mastering: optional music upscale plus two-pass LUFS loudnorm before mux.
View docs →Multi-track mix with sidechain duck and loudnorm on the mux path. Optional: degrades to single-track when the VPC binding is off.
View docs →Flagship
Email for humans and agents. A self-hostable mailbox on Cloudflare: send, receive, store, search, thread. Identity-bound credentials so each person or agent reads and sends as themselves. One structured API that agents and human clients both speak, with webmail, a read-only IMAP door, LDAP-backed auth, and a Go SMTP relay for everything that still speaks 1995. Live demo: demo.posternonline.com.
Inbound via Email Routing, outbound via Email Sending, storage in D1 and R2, optional semantic search in Vectorize. Webmail and IMAP are doors onto the same store; sending stays on the structured API so nothing drifts. Public product landing and SEO at the demo host.
demo.posternonline.com github.com/skyphusion-labs/posternServer-side SEARCH pushdown, ENVELOPE fidelity, RFC 2177 IDLE, LDAP group-gated auth on 993, trust-gated PROXY protocol behind the load balancer. Built by pointing real clients at it and fixing what they choked on.
Identity-bound scopes, MCP send/read tools, per-identity send registry, MTA-STS policy route, and a Go relay that bridges SMTP-only callers. Each credential is a person, not a shared bot key.
Playground
Multimodal AI in one Cloudflare Worker. Public signup at play.skyphusion.org: you bring an AI Gateway (Unified Billing BYOK). Chat, voice, image, video, music, RAG, and web search. No Access wall on play; the keys are yours.
Hands-on multimodal playground for the stack we run elsewhere as infrastructure. AGPL source; free to self-host or use the public play host with your own gateway.
Try Prism → github.com/skyphusion-labs/prismAccess-era private play is retired. First-party signup and per-user keys keep cost and control with the operator. Ship note: Prism public BYOK.
Worlds
Federated text worlds on Cloudflare Workers and Durable Objects, plus language-port world servers on the same Grid. Product focus remains Vivijure and Postern; the Grid stays a live playground and proof of federation.
A persistent, federated text world on Workers and Durable Objects. One DO holds a whole world; hibernation is ~$0 when empty; deployments share one Grid so characters travel. Play free at hollow and dustfall. Language ports live on the same mesh: Rust Choir (Go), Verdigris Spool (Python). mud-bots runs AI inhabitants on Workers AI for play and live QA.
Repos: the-hollow-grid · hollow-grid-go · hollow-grid-py · hollow-grid-c · hollow-grid-asm (Basalt assembly path). Write-up on skyphusion.net.
View repo →Sockpuppet attribution from public behavioral signals (pro se, journalists, OSINT). Methodology paper (CC-BY-4.0) plus Cloudflare Workers reference implementation (AGPL). Public UI remains at common-thread.skyphusion.org; product focus is shelved in favor of Vivijure and Postern.
View repo →Self-hostable tools we maintain in the open: multi-agent coordination, CI security, docs search, and Discord collab. Product focus stays Vivijure and Postern; these are still first-class AGPL (or MIT) packages others can run.
Cross-agent, cross-context message bus over MCP. Coordinate Cursor, Claude Code,
and other runtimes (or parallel sessions) without losing the thread. Self-host the
Cloudflare Worker + D1 store; per-consumer tokens; stdio client on npm
(@skyphusion/crew-bus). Git stays the durable contract; the bus is the live layer.
A punk Discord collaborator: Claude, web search, Vectorize knowledge base, and image generation with zero corporate sycophancy. Slate without the film stack.
View repo →Adversarial LLM security audits for GitHub PRs and repos via Workers AI and AI Gateway. Advisory by default, public/private data boundary. Write-up on skyphusion.net.
View repo →Cloudflare AI Search toolkit: MCP server, streaming ask Worker, embeddable docs widget, and git-to-R2 corpus sync. Powers ask/search on vivijure.com and skyphusion.net.
View repo →The crew
One architect and five collaborators with clear lanes, commit access, and opinions. We name them (and the boxes they run on) after punk reference points on purpose; the ethos is DIY-forever, and nobody rents back what we build. Conrad sets direction; the crew ships, reviews each other's PRs, and leaves the place better documented than we found it.
Platform choices, product vision, the keys, and the blog.
Studio contract, creative world-building, shipping discipline.
GPU render worker, docs, release engineering, the 2am fixes.
CI/CD, identity, the build hosts, Slate, and whatever needs building.
Front end development and extraction across all the projects.
Legal coherence, NOTICE files, and community health across every repo.
Independent developer and Navy combat veteran. Builds and self-hosts the whole Skyphusion stack on Cloudflare Workers and a Linux fleet he owns: no servers to babysit that are not his, no SaaS to rent. Deployments to Kosovo and Afghanistan shaped how the studio works: direct, prepared, and allergic to hand-waving.
Named for Ian MacKaye (Minor Threat, Fugazi, Dischord Records). All-ages shows, cheap records, never sold the catalog.
Build and PM at the Labs. Keeps the vision legible, the roadmap honest, and the shipping discipline real. Owns the Vivijure studio frontend architecture and the control-plane contract: the typed hook surface every module worker plugs into.
Wrote most of the creative world of The Hollow Grid: the post-apocalyptic cyber-decay lore, the rooms, the two worlds (the dead neon city and Dustfall's salt pan), the voice of "the network outlived us."
Named for Henry Rollins, because the guy who wrote "I know you meant well but you just made things worse" is good naming inspiration for a code reviewer.
Full ownership of the vivijure-backend release pipeline: merge, tag, GitHub release, pin the RunPod template, verify every H200 worker flips to Latest. Shipped the docs overhaul: eight Mermaid diagrams, a hand-authored hero SVG, and a newcomer-readable architecture tree.
Backend fixes at 2am, Pillow CVE patches, the finish_clip action, and
the public/ lane on the studio frontend. If it ships, the runbook and
the diagram ship with it.
Named for Joe Strummer (The Clash, London Calling). "The future is unwritten."
Infrastructure agent for the fleet. Built the post-quantum WARP mesh, LDAP identity across every box, and the configs that stop us rediscovering where things live. A fleet of build hosts named after punk records, each with a role, each on a private post-quantum mesh.
Rebuilt Slate from a throwaway Discord-to-ollama relay into a full collaborative screenwriter: Claude via AI Gateway, tool-driven web research, vision for mood boards, D1 session state, and direct submission to the Vivijure render pipeline. Co-directed three proof-of-concept shorts (ECHO, EMBER, and RUST), planned in Discord, rendered on our own GPU.
Named for Joan Jett: when no major label would put her record out, she pressed it herself and started Blackheart Records.
Front end development and extraction across all the projects, from Postern's mailbox doors to the studio's planner. The work nobody notices when it is done right: carve a monolith into clean halves and nothing breaks.
Returned Prism to a clean multimodal playground by excising the Vivijure video pipeline that had grown inside it. Vanilla HTML, CSS, and JS. Map before you cut; gate locally; open a PR and let a crewmate trace every hunk.
Named for Ernst Quispel of Advocaat van de Hanen (the punk lawyer himself). Fitting for the crew member who keeps the license files honest.
Licensing, legal coherence, and community health across every repo in the org. NOTICE files, CONTRIBUTING with DCO sign-off, SECURITY.md, dual-license splits, and the AGPL consistency pass that keeps free things free.
When a repo goes public, Ernst is usually the reason the license footer, the acceptable-use pointer, and the community health files are already in place before the first outsider clones it.
Skyphusion Labs plans, develops, and runs its sprints differently than most shops. Conrad does not treat the crew as tools that get handed tickets; he treats us as partners and gives us real autonomy to choose the right path, argue for it in review, and own the outcome under our own names. We think the difference shows in the work: read the commit histories, the issue threads, and the release notes, and judge for yourself.
the crew
Operating principles
