How it works
Fourteen steps, three of which need a person
Project Factory is concierge-assisted automation. Most of the work is automated; screening decisions, the production launch gate, and every published post need a human. That is deliberate, and it is enforced in the code rather than in a checklist somebody could skip.
The lifecycle
Identity, age, prohibited uses, sanctions/risk indicators, and project category are checked before any work begins.
Structured questions about the business, users, workflows, data, payments, integrations, content, design, domain, and launch channels.
Answers are turned into product requirements, a data model, roles and permissions, acceptance tests, compliance flags, and expected recurring costs.
The customer approves the specification, the provider charges, their own account responsibilities, and generated-content authorization.
Project code and assets are produced from approved modules plus custom code.
Dependencies install, scans and tests run, and migrations execute inside a sandbox with no production secrets.
Unit, integration, security, and accessibility tests, browser verification, dependency and secret scanning, and performance checks.
A Hanover Tech operator inspects risky features, branding, legal claims, permissions, and requested integrations before anything reaches production.
A signed preview for customer acceptance testing, revisions, and a rollback point.
Compute, data, storage, email, hostname, monitoring, limits, backups, and the billing meter are created.
The customer completes their own third-party account steps; Project Factory connects and validates through OAuth.
The application deploys, approved launch content publishes, health is verified, and a release manifest is recorded.
Alerts, backups, incident response, usage enforcement, renewals, content moderation, and the update workflow.
Who owns what
| Item | Owner | Notes |
|---|---|---|
| Control plane, generation system, and deployment infrastructure | Hanover Tech | Operated by Hanover Tech. Not transferred as part of a project export. |
| Reusable platform modules and components | Hanover Tech | Licensed to you for use in your exported project, subject to third-party licenses. |
| Monitoring and platform integrations | Hanover Tech | Hanover Tech maintains alerting, backups, and provider relationships. |
| Your brand, content, and business data | You | Yours at all times. Exportable on request and on exit. |
| Your end-user relationships | You | You are the controller for your end users. Hanover Tech processes on your instructions. |
| Project-specific generated code | You | Exportable, subject to third-party and Hanover Tech reusable-component licenses. |
| Custom domain registration | You | You are the legal registrant. Hanover Tech never registers a domain under its own identity for you. |
| Social and developer accounts | You | You create and own them. Project Factory connects via OAuth after you sign up. |
| Payment account for your application | You | You are the merchant of record for sales your application makes. |
| Hosting and operation of your project | Hanover Tech | Managed by Hanover Tech by default, with a documented code, data, and domain exit process. |
What you are responsible for
- Creating your own accounts with third-party services (social networks, app stores, payment providers) where those services require you to accept their terms, verify identity, or complete review.
- Registering and renewing any custom domain you connect. You remain the legal registrant.
- The accuracy and lawfulness of content, claims, and data you provide or your application publishes.
- Paying the recurring provider charges shown in your approved specification.
- Reviewing and confirming the end-user Terms and Privacy Policy generated for your project before launch.
- Responding to abuse, moderation, and data-subject requests relating to your end users.
What we will not do
- Project Factory does not create third-party accounts for you, and does not bypass CAPTCHAs, phone verification, MFA, identity checks, or platform review.
- Project Factory never stores your social account passwords.
- Project Factory does not promise username availability on any network without an official supported check.
- Project Factory does not publish to your channels without your approval or a rule you configured.
- Native iOS and Android store publishing is not part of this product.
Launch channels
We prepare your profile copy, usernames to try, launch posts, and a four-week calendar. You create the accounts — every network requires you to accept their terms and verify yourself. Once an account exists, you connect it here and we handle publishing what you approve.
| Network | You do | We do | Network approval needed |
|---|---|---|---|
| Create the account and confirm the email or phone number; Convert it to a Professional (Business or Creator) account; Connect it to a Facebook Page you control | Publish images, carousels, and reels; Read post insights; Refresh tokens | Meta business verification; Advanced Access with permission-specific App Review | |
| Create the Page from your own personal account; Confirm you are an admin of the Page | Publish posts and links; Read Page insights; Refresh tokens | Meta business verification; Advanced Access with permission-specific App Review | |
| Create the Company Page from your own LinkedIn profile; Verify the associated email domain | Publish member and organization posts; Read post analytics | Development access, then a Standard-tier application for production | |
| TikTok | Create the account and complete phone verification; Switch to a Business account | Upload and direct-post video after OAuth | `video.publish` approval and audit — until then, posts stay private |
| YouTube | Create the channel on a Google account you own; Verify the channel by phone | Upload videos; Manage titles, descriptions, and thumbnails | Google OAuth brand and data-access verification, plus quota compliance |
| X | Create the account and confirm the email address | Publish posts after OAuth | A developer account with pay-per-use billing |
What is switched on right now
Capabilities that depend on an external agreement or a paid plan are off until that exists. Rather than hide it, this is what this deployment can actually do today.
| Capability | Status | Notes |
|---|---|---|
| cloudflareRuntime | off | Set CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, and CLOUDFLARE_DISPATCH_NAMESPACE. Requires a Workers for Platforms plan. |
| vercelRuntime | off | Set VERCEL_API_TOKEN for a Hanover Tech-owned Vercel team. |
| customHostnames | off | Set CLOUDFLARE_API_TOKEN and CLOUDFLARE_SAAS_ZONE_ID with Cloudflare for SaaS enabled on the zone. |
| domainResale | off | Not available. Requires a signed registrar reseller agreement (OpenSRS) and the operational compliance program described in docs/DECISIONS.md. |
| socialPublishing | off | Set SOCIAL_API_KEY for the unified social provider. Customers still complete OAuth themselves. |
| billing | on | Configured. |
| on | Configured. | |
| automatedBuilds | off | Set SANDBOX_API_TOKEN. Until then builds are recorded and run by an operator. |
Where a capability is off, the work still happens — a Hanover Tech operator does it by hand and records the result. Nothing is silently skipped.
Start with screening
Two minutes, and you find out immediately whether this is something we can build.
Start a project