FAQ
Plain answers.
Explicit boundaries.
What Firequark builds, what Growth OS currently is, how checkout works and what requires a custom agreement.
Company
What Firequark is
Is Firequark a marketing agency?
No. Firequark is a software development company. We build software that may support content, websites, local visibility, reviews, leads and growth workflows, but we do not present campaign management as our core service.
What can Firequark build?
Web and mobile applications, portals, integrations, business automation, data systems, commerce flows, operational tools, modernization work and industry-specific software.
Where is Firequark located?
The business address published on this site is 2119 N 1060 W, Provo, UT 84604.
Growth OS
Product status
Is Growth OS available?
A DreamHost shared-host controlled beta is available for authorized evaluation. It is explicitly labeled non-production-grade and keeps external reads and writes off unless separately authorized.
Does Growth OS replace field-service or accounting software?
Not initially. It is designed as an evidence-backed control layer that can integrate with established operational systems instead of pretending to replace every mature category.
Can beta fixtures prove business results?
No. Synthetic or fictional records verify software behavior; they do not prove market demand, client outcomes or attribution.
Shop and checkout
Purchasing
Where are card details entered?
On Stripe-hosted Checkout. Firequark's website does not contain card fields or store card numbers.
Does adding an item start delivery?
No. Firequark confirms scheduling, prerequisites and the delivery contact after checkout. A custom build still requires a separate accepted scope.
Is checkout live?
The initial release uses Stripe sandbox for technical verification. The interface must not be interpreted as accepting a real payment until live mode is separately approved and clearly enabled.
Delivery
Building software
Can you work with an existing codebase?
Yes, subject to access and an initial review. A technical audit is often the safest first scope.
Who owns the code?
Ownership and any reused or third-party components are defined in the project agreement. Do not rely on a general website statement in place of contract terms.
How is security handled?
Requirements are translated into system boundaries, server authorization, least privilege, protected secrets, audit evidence and risk-appropriate tests. No website can guarantee absolute security.
Ignition
Ask the question behind the question.
If a technical, commercial or operating boundary is unclear, contact Firequark before submitting payment or sensitive information.