Fair Use Policy
Learn what use is allowed on Nitroship, what is prohibited, usage limits, and how to report issues.
This is a translation; the Korean version prevails.
Effective date: 2026-10-01
This policy sets out how to use Nitroship safely and fairly. Members should ensure that apps and member content deployed by them and their team members meet these standards.
Article 1 (Scope and relationship to the Terms)
This policy is part of the Nitroship Terms of Service and applies to all members, teams, apps, and deployments. When the company changes this policy, it will announce the effective date and changes; changes unfavorable to members will be announced at least 30 days before taking effect. The Terms of Service govern restrictions on use and termination.
Article 2 (Normal use)
Members may deploy web apps, APIs, and static sites and configure scheduled tasks (cron jobs) for their own apps while complying with applicable law and the rights of others. Members must provide their app users with required notices and consents and manage their apps' content and access permissions. Commercial-purpose apps and services may also run on the Free plan. The Pro plan is not required solely because of commercial use; the same usage and prohibited-conduct rules in this policy apply.
Article 3 (Prohibited conduct)
Members must not use Nitroship services, apps, or member content for the following activities or help others do so. These prohibitions cover not only unlawful acts but also service-use rules that protect shared infrastructure.
- Storing or distributing illegal intimate images, child sexual exploitation material, or content that infringes another person's copyright or other rights, or providing illegal gambling services
- Phishing, fraud, payment card testing, or use of another person's payment method without authorization
- Spam or bulk email or messaging without recipients' consent
- Distributing malware or operating botnet command-and-control (C2) or DDoS attack tools
- Scanning, penetration testing, load testing, or accessing targets without authorization
- Operating open proxies, VPNs, Tor exit nodes, or mail relays available to anyone
- Using torrents, file mirrors, or hotlinking to evade bandwidth limits or charges
- Cryptocurrency mining
- Using multiple accounts, disposable email addresses, or automated sign-ups to repeatedly obtain free allowances or credits. Legitimately operating multiple teams or apps is not prohibited by itself.
- Evading usage limits, charges, authentication, or security measures
- Reselling Nitroship compute resources without the company's prior written agreement. This does not mean offering your own app to its users.
- Disrupting another member's service or the normal operation of shared infrastructure
- Mass-crawling a target other than your own app without respecting its robots.txt or rate limits
Article 4 (Monthly usage allowances)
These are the initial Free plan allowances per billing cycle. Check the console's pricing schedule and billing information for the plan, allowances, regional rates, and calculation rules that actually apply to your team. The pricing schedule published by the operator for the relevant cycle takes precedence over these examples.
| Metric | Free allowance | What it measures |
|---|---|---|
| Fast Data Transfer | 100 GB/month | Bidirectional traffic between clients and the edge |
| Edge Requests | 1 million/month | Public requests attributed to an app |
| Fast Origin Transfer | 10 GB/month | Billable bidirectional traffic between the edge and compute or external origins (excluding CDN object reads) |
| Compute CPU | 4 CPU-hours/month | CPU time actually used |
| Compute Memory | 360 GiB-hours/month | Provisioned memory multiplied by billable time |
| Compute Invocations | 1 million/month | Invocations admitted to compute |
A GB is one billion bytes. Edge requests and compute invocations are separate metrics. These displayed allowances do not mean that billed plans have unlimited free usage.
Article 5 (Plan-specific size limits)
The following are the initial size limits for the Free and Pro plans. The operator may update the plan catalog, so the limits published in the console for the applicable plan take precedence. Requests or uploads exceeding a limit may be rejected.
| Item | Free | Pro |
|---|---|---|
| Function request body | 4,500,000 bytes | 4,500,000 bytes |
| Function response body (with Content-Length) | 4,500,000 bytes | 4,500,000 bytes |
| Total uncompressed regular source-file size for CLI uploads | 100,000,000 bytes | 1,000,000,000 bytes |
| Regular source-file count | 15,000 | 15,000 |
| Single function bundle | 250,000,000 bytes | 250,000,000 bytes |
The function response limit applies to responses with Content-Length, not to streams with unspecified length. CLI-uploaded source size is measured as the total of uncompressed regular files. For builds from Git repositories, only the source-file count limit applies.
Article 6 (Overages and shared-infrastructure protection)
Non-invoiced plans do not charge for usage above allowances, but production apps may be paused where the plan's included-usage limit and billing enforcement apply. Invoiced plans may charge for excess usage according to the pricing schedule. CDN billing modes differ in the items and timing they cover, so check the applicable pricing schedule and billing screen. Usage measurements may be delayed, and a spending budget is not a guaranteed cap on every charge. If reasonable restrictions such as request-rate limits are needed to keep shared infrastructure safe, the company will generally contact members beforehand. Urgent cases follow the emergency-restriction procedure in the Terms of Service.
Article 7 (Security testing and vulnerability reports)
Members may perform low-impact security testing only on their own apps or apps they are explicitly authorized to operate, without affecting other users. Scanning, penetration testing, or load testing the Nitroship platform itself requires the company's prior written approval through team@nitroship.co. Report vulnerabilities privately to that address with '[보안]' in the email subject. Do not disclose a vulnerability before giving the company a reasonable time to respond, or access, alter, or delete anyone else's data. The company will not penalize good-faith security research solely for complying with these rules.
Article 8 (Reporting abuse or rights violations)
Report abuse or rights violations to team@nitroship.co. Use the applicable subject tag '[악용 신고]', '[권리침해]', or '[보안]' and include the target URL and domain, the grounds for the reported violation or infringement, supporting information, and your reply contact details. The company will review the report and determine necessary action under applicable law and the Terms of Service.
Article 9 (Response to violations and appeals)
The Terms of Service provisions on restrictions govern the criteria and contractual effects of a restriction. Wherever possible, the company will consider the smallest necessary scope, prioritizing a deployment, domain, or app. For a correctable violation, it will notify the member of the reason, affected resource, and remedy and provide seven days to correct it. If a security breach, payment fraud, legal requirement, or imminent harm to another member is involved, it may immediately restrict only what is necessary and notify the member without delay afterward. Members may appeal to team@nitroship.co; the company will review lifting a restriction once its cause is resolved.
Article 10 (Supplementary provision)
This policy takes effect on 2026-10-01.