Don't see what you need?
Tell us your industry, target markets, and tech stack. We deliver standard products fast — and custom development, integrations, on-prem deploys, and global go-to-market when you need more.
Recreate means new, maintainable code that looks and runs like the reference — not lifting someone else’s site, app, or commercial game. Rights check first.
Who it fits
- ▹Lost source or heavy debt — needs to look the same and keep the main path
- ▹Design or recordings are done; you want a faithful build, not a blank-canvas product
- ▹Same class of experience under your brand — style only, no third-party marks or assets
- ▹Owned or licensed IP: an H5 / mini-game demo, then levels
We will not take
- ▹Unauthorized copies of others’ sites, apps, or games for commercial use
- ▹Decompile, crack, watermark strip, DRM bypass
- ▹Counterfeits users cannot tell from the original
- ▹No reference and no rights — “1:1 the competitor”
Three main tracks
Say whether it is a site, an app, or gameplay. Send assets and rights together.
Sites
Corporate, landing, storefront, admin skin. Page-by-page, responsive, motion close to reference.
- ·Live site, no source
- ·Design-file build
- ·Stack change (e.g. WP → Next.js)
Apps & mini-programs
H5, WeChat mini-program, desktop. Login, list, detail, one core flow first.
- ·Your build or recording
- ·Legal API rewiring
- ·Can stack custom software
Game prototypes
Owned or licensed gameplay as H5 / mini-game. No cracked commercial titles.
- ·One playable level
- ·Level and economy iteration
- ·Assets you own or may use
Rights & assets
URLs, accounts, design sources, license letters. No quote until this clears.
- ·Ownership or license
- ·No stolen marks/assets
- ·Competitors as style notes only
Side-by-side QA
Reference next to the new build. Must-match / can-simplify / out-of-scope.
- ·POC one path
- ·Sprint reviews
- ·Written acceptance
Stack with other packs
Recreate is “looks like it”. Content, payouts, lines, greenfield systems stay on their pages.
- ·Glynx / store builds
- ·Software & custom
- ·Dedicated line is connectivity only
Four grades
Do not buy the full stack first. Grade, then a POC to see if it looks right.
L1 Look-alike
Brand and landing pages, admin skins. Pixel-close, responsive, motion. No heavy business logic.
L2 Site equivalent
Corporate / storefront / CMS. Routes, forms, a checkout or lead path, editable admin. No cracking private APIs.
L3 App rebuild
Mini-program, H5, desktop. Login, list, detail, legal APIs. Decompile is not a deliverable.
L4 Gameplay prototype
Owned or licensed IP. Playable H5 / mini-game demo, then levels. No commercial console/PC cracks.
What to send
Web
- ▹URL or export
- ▹Brand / Figma / cuts
- ▹Forms and admin that must stay
App
- ▹Your build or recording
- ▹Accounts and staging
- ▹Legal API docs to rewire
Game
- ▹Gameplay note or license
- ▹Owned or licensable art
- ▹Target: H5 / mini-game / campaign
How we start
Written origin: owned, licensed, or style-only without their marks/assets. No quote otherwise.
Screens, motion, APIs, data, admin. Must-match / simplify / skip. Grade in 24h.
3–7 days: one main path or one level. POC can be billed alone.
Sprints against the reference. Asset gaps listed in writing.
Source in scope, deploy, training. Later work can move to software/custom.
Deliverables
- Rights note and scope list
- POC (one path or one level)
- Side-by-side acceptance sheet
- Source and deploy notes in scope
- Asset and third-party API list (you provide)
Send the reference and rights note
then we pick L1–L4
Site, app, or game — attach a URL, design, or recording you have rights to. Grade and POC advice in 24 hours. No unauthorized clones.