1+ ---
2+ toc_min_heading_level : 2
3+ toc_max_heading_level : 2
4+ ---
5+
16# Provisioning Options
27
38The creation wizard for Satellites and Orbiters includes advanced provisioning options for developers who need more control.
49
510---
611
7- ## Hosting Memory
12+ ## Website vs Appliction
813
914When you initialize a satellite, you must decide how the frontend will be kept in memory and served on the web.
1015
@@ -30,6 +35,28 @@ For more background on memory behavior and limits, see the [Memory](./memory.md)
3035
3136---
3237
38+ ### Summary
39+
40+ The table below summaries the difference regarding the ** hosting memory** .
41+
42+ :::note
43+
44+ This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.
45+
46+ :::
47+
48+ | | Website (heap) | Application (stable) |
49+ | ------------------------- | --------------------------------------------------------- | --------------------------------------------------------- |
50+ | ** Best for** | Websites, blogs, content sites | SPAs, feature-rich applications |
51+ | ** Speed** | Faster, more consistent | Slightly slower on average, spikier under load |
52+ | ** Asset size limit** | ~ 1 GB (serialization on upgrade) | No practical limit |
53+ | ** Upgrade cost** | Assets re-serialized on every upgrade | Assets survive upgrades without re-processing |
54+ | ** SEO impact** | Better (lower TTFB, ~ 0.5 s faster LCP) | Minor overhead (~ 0.5 s added to CWV) |
55+ | ** Default in Console** | ✅ Website | ✅ Application |
56+ | ** Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |
57+
58+ ---
59+
3360## Selecting a Subnet
3461
3562If you want more control over where your module is provisioned, you can select a [ subnet] during the creation process.
0 commit comments