macrostack
Browse

The AI stack

Categories

Local & Sovereign AINotes & KnowledgeObservability & MonitoringPassword ManagersWeb AnalyticsTeam ChatSmart HomeNetworking & RoutersVideo ConferencingCloud Storage & SyncPhotos & MediaAPI DevelopmentImage EditingWorkflow Automation & iPaaSDeveloper Tools & ContainersOffice & Productivity SuitesNo-Code DatabasesCode Hosting & Git ForgesProject ManagementEmail Marketing & NewslettersScheduling & BookingError Tracking & Exception MonitoringLog Management & SIEMVPN & PrivacyEmail & Secure MailVector Databases & AI SearchLLM & Agent FrameworksDomains & Web HostingData Removal & PrivacyAuthentication & IdentityHelp Desk & Customer SupportCloud & VPSKubernetes & Container PlatformsEmbedding ModelsPDF & DocumentsAI Coding AssistantsAI Voice & SpeechLLM Observability & EvaluationLLM Gateways & RoutingCloud GPU & AI ComputeCI/CD & build automationData & pipeline orchestrationModel serving & inferenceAI agent frameworksBackend as a serviceSecrets managementFeature flags & experimentationProduct analyticsSearch infrastructureUptime & status monitoringAffiliate & partner platformsVisitor identification & personalisationWikis & internal docsIdentity & access managementData warehouses & analytics enginesCustomer data platformsCRMObject storageBI & dashboardsE-signatureWhiteboards & diagrammingIn-memory data stores & cachingPlatform as a serviceTransactional & bulk emailHeadless CMSDesign & prototypingE-commerce platformsInternal tools & admin panelsManaged databasesForms & surveysFine-Tuning & Model TrainingRAG & Retrieval PlatformsLLM Evaluation & TestingAI Guardrails & Content SafetySpeech Recognition & TranscriptionExperiment Tracking & ML OpsDocument AI & OCR

About

How we rank & score

Layer 3 · self-hosting reality check

What it actually takes to self-host GrowthBook

The docs say 2 GB. In practice you want 4 GB. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.

Usually reached from LaunchDarkly alternatives, where GrowthBook is one of the picks.

RAM — documented minimum2 GB
RAM — what it really needs4 GB
CPU2 vCPU
DiskSmall — it queries your warehouse rather than storing events
Monthly cost$20–35/mo, against LaunchDarkly pricing that starts high and scales per seat and per MAU
Setup time2 hours
How you install itdocker compose — app, MongoDB, and a connection to your existing data warehouse
Ongoing maintenanceLow to moderate.
Where it stops scalingLarge experiment volumes, because the heavy lifting happens in your warehouse rather than in GrowthBook.

The thing that catches people out

The architecture is its best feature and the thing people miss: GrowthBook does not ingest your events, it queries your warehouse where they already are. That means no duplicate data pipeline — but it also means experiment results are only as good as the warehouse behind them, and a badly modelled events table produces confidently wrong statistics. Validate one experiment by hand before trusting the platform.

When not to self-host GrowthBook

You have no data warehouse. GrowthBook assumes your events live somewhere queryable; without that, it has nothing to analyse.

Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.

Other Layer 3 self-hosting guides

Common questions

How much RAM does GrowthBook actually need?
4 GB in practice. The documented minimum is 2 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU alongside it.
What does self-hosting GrowthBook cost per month?
$20–35/mo, against LaunchDarkly pricing that starts high and scales per seat and per MAU This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for low to moderate.
How long does it take to set up GrowthBook?
2 hours, via docker compose — app, MongoDB, and a connection to your existing data warehouse.
When should I NOT self-host GrowthBook?
You have no data warehouse. GrowthBook assumes your events live somewhere queryable; without that, it has nothing to analyse.
What is the most common mistake when self-hosting GrowthBook?
The architecture is its best feature and the thing people miss: GrowthBook does not ingest your events, it queries your warehouse where they already are. That means no duplicate data pipeline — but it also means experiment results are only as good as the warehouse behind them, and a badly modelled events table produces confidently wrong statistics. Validate one experiment by hand before trusting the platform.
The Macrostack brief

New swaps, worth your inbox.

A short, occasional email when we add a high-intent alternative or ship a new head-to-head. No spam, no selling your address — unsubscribe in one click.