Deployment

The public host split for the current beta.

OwlyVision is intentionally split across multiple public surfaces so the brand, product runtime, and documentation stay cleanly separated.

Domain model

  • owlyvision.com is the canonical public marketing surface.
  • app.owlyvision.com is the product runtime for briefs, APIs, share links, and exports.
  • docs.owlyvision.com is the documentation surface.
  • owly.vision is a supporting brand asset, not the main canonical product host.

Runtime shape

The current beta uses one live application runtime for the app surface, while the docs surface lives on a separate static Hostinger subdomain so documentation delivery stays decoupled from the product runtime.

  • The app host needs a long-running runtime, healthchecks, and persistent state.
  • The docs host is static in content and fits well on a Hostinger-managed subdomain with platform SSL.
  • The marketing apex can stay separate so legacy redirects and SEO control remain deliberate.

Indexing and canonical ownership

  • Marketing pages canonically belong to owlyvision.com.
  • Docs pages canonically belong to docs.owlyvision.com.
  • Private app/share surfaces should stay noindex.
  • The docs surface should have its own robots and sitemap behavior rather than inheriting marketing rules.

Legacy path preservation

OwlyVision still carries legacy outbound-preview traffic from the earlier automation system. Because of that, apex changes must preserve the redirect paths that were explicitly moved elsewhere rather than treating the root domain as a blank slate.

Practical operating rule

Use this split

Keep brand and SEO intent on the apex. Keep the product runtime on app.. Keep docs on docs.. Only use owly.vision for support, redirects, or shortlink behavior.