# Disable frontend when using Ghost as a headless CMS **URL:** \ **Category:** Developer help\ **Created:** [February 26, 2019, 8:24pm UTC](https://forum.ghost.org/t/disable-frontend-when-using-ghost-as-a-headless-cms/5915 "2019-02-26T20:24:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jobbogamer](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jobbogamer/32/2679_2.png) [@jobbogamer](https://forum.ghost.org/u/jobbogamer)\ **Post date:** [February 26, 2019, 8:24pm UTC](https://forum.ghost.org/t/disable-frontend-when-using-ghost-as-a-headless-cms/5915/1 "2019-02-26T20:24:29Z")
I’m looking to use Ghost as a headless CMS for a Gatsby frontend hosted on Netlify. My question is although it’s very easy to get Gatsby working with Ghost, is there a way to disable Ghost’s frontend entirely? I know about making it “private” with a password, but ideally I’d like for Ghost to serve only as a CMS with no frontend at all. Is that possible? ---
**Author:** ![Kevin](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kevin/32/32_2.png) [@Kevin](https://forum.ghost.org/u/Kevin)\ **Post date:** [March 4, 2019, 9:42am UTC](https://forum.ghost.org/t/disable-frontend-when-using-ghost-as-a-headless-cms/5915/2 "2019-03-04T09:42:53Z")
Putting the site in private mode is the recommended option, if you want to lock it down further then you could modify your nginx/apache config so that it only serves the `/ghost/*` endpoints for the admin and API and `/content/*` for images etc. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/2X/b/ba9ce5100b8bb264586f4f572545596b2ce3f081.png) [@system](https://forum.ghost.org/u/system)\ **Post date:** [March 18, 2019, 9:55am UTC](https://forum.ghost.org/t/disable-frontend-when-using-ghost-as-a-headless-cms/5915/3 "2019-03-18T09:55:07Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.