A security-first roadmap for author publishing tools
Our existing services and calculators work without Cloudflare. We are evaluating additional edge protection, storage and asynchronous processing for future author workflows while retaining the Railway application.
Next.js on Railway provides service descriptions, interactive estimates and inquiry flows. No Cloudflare migration is part of these pages.
Today: data and operations
The existing website APIs use Firestore and Zendesk. A separate operations CRM has Firebase and Airtable responsibilities.
Potential edge layer
Cloudflare DNS, CDN, WAF and DDoS protection could secure and accelerate the public website without replacing the current host.
Future file workflows
Cloudflare R2, Workers and Queues could support authorized manuscript files and background checks if those capabilities are separately implemented and reviewed.
PRODUCT INFRASTRUCTURE
Building a reliable experience for independent authors
Our publishing tools and inquiries use an existing application stack. We are evaluating Cloudflare for edge protection and future file-heavy workflows without replacing the software already in use.
AVAILABLE TODAY
Working website and APIs
Next.js on Railway serves the publishing catalog, pricing tools and inquiry forms. Existing server routes connect inquiry records to Firestore and Zendesk. The separate CRM is an operations tool.
Additional security, content delivery, private file storage and asynchronous work are under evaluation. This is a proposal, not a claim of active Cloudflare services or a partnership.
Assess Cloudflare DNS, CDN, DDoS protection and WAF rules for our public site while Railway continues to serve the application.
Future capability
Private author-file storage
Explore R2 for manuscripts and production assets if secure upload is implemented. Private objects, limited access and malware scanning come first.
Future capability
Server-side edge functions
Explore Workers for validated, short-lived upload permissions and narrowly scoped callbacks. Credentials would never be exposed in the browser.
Future capability
Asynchronous processing
Explore Queues for retryable file checks and workflow events once actual upload and processing pipelines are built.
Illustrative architecture
Author browser → proposed Cloudflare edge/CDN/WAF → existing Railway website and API → existing Firestore and ZendeskFuture, separate private-file flow: authorized upload → time-limited R2 access → scanning and review → approved, authorized retrieval. Queues could coordinate background tasks.This is not an active upload or processing system. Separate engineering, privacy review, testing and deployment approval would be required.