Morphin is being rebuilt as a cleaner single-site platform.

Create image and video experiences from one modern control center.

Morphin now runs as one focused Next.js product: marketing pages, admin panel, and backend API in the same app. That keeps content management simple and deployments predictable.

01

One app for landing, panel, and API.

02

Shared management model for image and video.

03

Push-to-deploy flow already wired to Hetzner.

Unified content model

Same management flow, different generation targets.

image
Image generation

Preset cards, credits, prompts, and active state controlled from admin.

video
Video generation

Parallel content type with its own rendering pipeline but the same management model.

Features

What the rebuild optimizes for

Single app architecture

Landing pages, admin screens, and backend routes live inside one Next.js app.

Shared generation model

Image and video content types share credits, visibility, ordering, and publishing rules.

Production ready deploy

Every push to main syncs only site/ to Hetzner, builds it, and restarts PM2.

Workflow

A simpler operating model.

Instead of splitting the project into separate systems, Morphin now uses one application and one deploy path. That keeps product work fast without losing control.

1

Choose a generation type

Every experience starts from a clean split: image or video. Both live in the same system.

2

Control credits and visibility

Each entry has credits, active state, ordering, and publishing controls from one admin flow.

3

Ship instantly

Push to GitHub, let Actions deploy the site, and keep landing, admin, and API aligned.

Why This Setup

Built for a small team that wants speed.

Single-site architecture

No split-brain deploys.

Marketing edits, admin improvements, and API updates can ship together. That keeps the product coherent and removes the overhead of coordinating multiple apps.

Landing pages and admin share the same design system
API routes stay close to the UI that consumes them
Production deploy stays simple enough to debug quickly

One codebase

Landing pages, admin tools, and API routes are deployed together and stay in sync.

Safer operations

Common rules like active state, credit cost, and ordering are managed from a single source.

Faster updates

Content and feature changes go live without juggling separate projects or servers.

Stack

One deployment target, zero panel sprawl.

Routes/, /admin, and /api/* in the same application.
DeployGitHub Actions pushes only site/ and restarts the production process automatically.

Ready

The first live landing page is now part of the app.

Next up is wiring the real content model: image/video entries, credits, active state, ordering, and admin actions on top of the current foundation.