# Should I deploy a site, an app, or a function?

Canonical URL: https://help.iagenify.com/faqs/hosting/should-i-deploy-a-site-an-app-or-a-function

[← Back to Hosting FAQs](https://help.iagenify.com/faqs/hosting)

HELP CENTER · FAQ Hosting 2 min read
# Should I deploy a site, an app, or a function?
The deployment type should match what must happen when a visitor makes a request. Static files, an application with server-side behavior, and a request-handling function have different needs and should not be treated as interchangeable packages.
IaGenify
Hosting

## Match the deployment to the project
A site deployment fits a built frontend whose pages and assets can be served as files. Use it when the browser can render the experience without your own server-side code running for each request. This is a straightforward fit for documentation, portfolios, and many marketing sites.
An app is appropriate when the project includes frontend files and a server module that must run to produce behavior or responses. A function is a narrower choice when the deployment is centered on code that handles incoming requests. Identify which code must execute on the server before choosing the deployment shape.
## Check the package before publishing
Review the build output and confirm the required entry page, assets, and server component are included in the right places. Keep secrets and local configuration out of public files; use the application's supported configuration path for sensitive values. Test the exact deployment type with a small release before attaching a custom domain.
If you are unsure, start from the project's actual build output rather than its framework label. A framework can produce static assets, server code, or both depending on its configuration. Choose the smallest deployment type that supports the behavior you need, then verify the published address and the routes that depend on server behavior. [← Back to Hosting FAQs](https://help.iagenify.com/faqs/hosting)