Skip to content
Historical revision — this record as it stood on 12 May 2026, not the current version. View the current record →

app-mediakit-marketing

app-mediakit-marketing serves multi-tenant marketing landing pages from a single statically-compiled Rust binary — no PHP, no MySQL, no plugin infrastructure — while preserving WordPress.org muscle memory at the operator-facing URL and navigation surface. The application shipped at v0.0.1 in May 2026 and runs two simultaneous production tenants — Woodfine at home.woodfinegroup.com and PointSav at home.pointsav.com — from the same binary on a single low-cost virtual machine, separated only by environment-variable configuration.

Function

The server presents each tenant's public marketing presence at a configurable domain. WordPress muscle-memory is preserved at the UX layer: the admin interface exposes Dashboard, Pages, Media, and Themes vocabulary familiar to anyone who has operated a WordPress site. Internally the application uses no PHP, no MySQL, and no plugin infrastructure.

Each tenant instance reads content from a configurable flat-file content directory and serves pages, media assets, and structured metadata over HTTP. A single compiled binary serves both the Woodfine and PointSav tenants through environment variable configuration.

Architecture

app-mediakit-marketing follows the PointSav leapfrog-2030 pattern:

  • Substrate: Rust + Axum web framework; statically linked binary
  • Content layer: Flat-file content directories; no database dependency
  • DataGraph references: Entity references resolved against the PointSav DataGraph at runtime
  • Multi-tenant routing: Tenant identity (TENANT_ID) configured via environment variable; a single binary instance serves one tenant
  • WordPress UX surface: Route vocabulary (/wp-admin/, /wp-admin/post.php, /wp-admin/upload.php) and navigation labels match WordPress.org conventions at the HTTP layer

Deployments

Two simultaneous production deployments operate on the foundry-workspace VM:

Deployment Tenant Domain Port
media-marketing-landing-1 Woodfine home.woodfinegroup.com 9102
media-marketing-landing-2 PointSav home.pointsav.com 9101

Both instances serve from the same binary, separated by environment variable sets in each systemd unit.

Version State

v0.0.1 delivers the core multi-tenant server, WordPress-compatible navigation, and basic flat-file content serving. DataGraph entity integration, media upload handling, and the full WordPress-equivalent admin dashboard are planned for subsequent milestones.

Tier Compatibility

The server is Tier 0 compatible: it runs on a single low-cost VM alongside other PointSav substrate services without requiring dedicated compute. Both deployments run concurrently on the foundry-workspace VM (e2-medium, 2 vCPU, 4 GB RAM).

See Also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →