1. Operator and contract
Botkeep is a digital service operated by TRAMA BENEVENTO SRL (the “Operator”, “Botkeep”, “we” or “us”). These Terms govern the website, account area, dashboard, workload hosting, source imports, file storage, logs, support and related features that Botkeep makes available (the “Service”).
These Terms apply when you accept them to register, order or use a hosting service. The accepted order or written Partner agreement specifies your allocation, price, duration and any additional commitments. Specific agreed conditions prevail over general descriptions; mandatory law always prevails. If you do not accept the applicable conditions, do not submit the registration or order. Only enabled profiles can be provisioned; displaying a profile does not reserve capacity.
| Company detail | Information |
|---|---|
| Legal name | TRAMA BENEVENTO SRL |
| Registered office | Piazza Maria Montessori 11, 80011 Acerra (NA), Italy |
| Operating office | Via Colonnette 2, floor 2, 82100 Benevento (BN), Italy |
| VAT identification number | IT08583941219 |
| Italian tax code | 08583941219 |
| REA / Chamber of Commerce | NA - 969486 / Naples |
| Share capital | EUR 10,000.00, approved, subscribed and fully paid |
| General and privacy contact | [email protected] |
| Certified email (PEC) | [email protected] |
2. Eligibility and minors
You must have legal capacity to enter this agreement. A person under 18 may use the Service only where a parent or legal guardian validly enters into the agreement, supervises the account and accepts responsibility for its use. No person may use Botkeep below any higher minimum age required by applicable law or by the third-party platform connected to the workload.
Botkeep may request proportionate information to verify eligibility where reasonably necessary. Accounts that cannot satisfy these requirements may be restricted or closed.
3. Accounts and access
You are responsible for activity performed through your account except to the extent caused by a failure attributable to Botkeep. An account grants a limited right to use the Service and does not transfer ownership of infrastructure, slots, identifiers, addresses or features.
Use the server and project Permissions features to authorise collaborators instead of sharing your password. Grant only the permissions they need. The account owner remains responsible for authorised resource use and charges. Removing access does not recall files or credentials already copied; rotate compromised credentials. A shared household, connection or device is not, by itself, proof of abuse.
- Provide accurate and current account information.
- Protect passwords, provider accounts, recovery methods and active sessions.
- Do not sell, rent, share or transfer an account without written authorisation.
- Notify Botkeep promptly of suspected unauthorised access or compromised credentials.
- Do not create multiple accounts to evade slots, sanctions, quotas or verification measures.
4. Hosting scope and availability
Botkeep is designed to host supported applications, workloads, databases, websites and service profiles. Enabled profiles include application runtimes, Redis, PostgreSQL, MySQL, MariaDB, static and PHP websites, Lavalink and Uptime Kuma. MongoDB is not enabled. The creation form shows the currently approved versions. A catalog entry does not guarantee suitability or performance for a particular workload.
This is managed hosting on shared infrastructure, not ownership or exclusive rental of a physical server. Unless an order or separate written service-level agreement states otherwise, no particular uptime percentage, startup time, dedicated processor, node location or uninterrupted availability is promised. Clearly identified beta features may change or be withdrawn. This does not remove agreed paid-service obligations or statutory conformity rights.
Choose a service suitable for your project and maintain recovery arrangements. Botkeep is not designed as the sole system for emergency, safety-critical, medical or other operations where interruption or data loss could cause serious harm. Published compatibility does not guarantee that your code, package or database will work with every version or a very small resource allocation.
5. Free, Founder Free and resource allocations
The Free plan includes up to two server slots per account with total account budgets of 1 GB RAM, 1 vCore (100% CPU) and 1 GB storage. On every plan, resources may be divided between servers or assigned entirely to a single server, subject to capacity already reserved for other servers, including stopped servers. Each database deployment occupies one normal server slot, with no separate database-count quota, and shares the same RAM, CPU and storage budget. Allocations follow the common resource selector; very small allocations may be insufficient to start or operate a particular engine. Free slots are intended for continuous operation without a periodic manual server-renewal requirement. A displayed allocation is a maximum permitted use, not dedicated hardware or a guarantee that the full allocation is continuously available.
Botkeep may apply reasonable queues, inactivity rules, build limits, network restrictions, log limits and fair-use controls. Material reductions will be communicated in advance where reasonably possible. Immediate limits may be applied for active abuse, security incidents, infrastructure failure or legal obligations.
Eligible registrations from 1 October 2026 at 17:00 until 15 October 2026 at 17:00, Europe/Rome, receive Founder Free: five hosting slots, a total pool of 2 GB RAM, 1.5 vCore (150% CPU) and 2 GB storage, two backups per service, 14 days of advertised backup retention and the Botkeep Founder badge. No card or Discord connection is required. The free entitlement has no recurring price or scheduled expiry: the end of the registration offer does not turn existing Founder accounts into paid accounts or ordinary Free accounts.
Founder Free remains subject to lawful use and the proportionate operational measures in these Terms. It is not a promise of dedicated hardware or uninterrupted service. General change clauses do not authorise silently replacing the advertised Founder allocation or introducing a fee. Any change must respect the original commitment and applicable law.
Custom and staff-assigned plans use the resource pool, slots, backup allowance, duration and conditions recorded for that assignment. A plan name alone does not promise extra resources, a service-level agreement or a permanent grant. Unless expressly agreed, Free, Founder, Partner and paid pools do not stack on one account. A change of plan does not create a second allowance.
Renewal or inactivity requirements, when applicable to a particular free offer, must be disclosed before assignment or introduced with the notice and protections in section 13. The existence of a staff control does not itself change a customer’s agreed conditions. Capacity limits may pause new registrations or server creation without revoking resources already promised.
6. User code, files and instructions
You retain the rights you hold in code, configuration, files and other content supplied to Botkeep. You grant Botkeep a limited, non-exclusive licence to host, copy, build, execute, transmit, back up, migrate and technically modify that content only as necessary to provide, secure and maintain the Service, follow your instructions, enforce these Terms or comply with law.
You confirm that you have the rights and permissions required for everything you upload or connect, including repositories, packages, libraries and personal data. You remain responsible for the behaviour of your workload, the data it collects, its commands, messages and compliance with Discord, GitHub and other third-party rules.
7. Tokens, secrets and credentials
Never place a live token in public source code, ordinary logs or support messages. Environment values are encrypted in the API database and delivered to the assigned runtime, including through a .env file that your application must load where required. This is not zero-knowledge or end-to-end encrypted hosting.
The application, its dependencies and people with appropriate file or infrastructure access may read runtime credentials. Masking a value in a form does not protect it from an authorised collaborator who can read the underlying file. Revoke compromised Discord, GitHub or other tokens with their issuer and rotate database credentials where needed.
8. Acceptable use
You must use Botkeep lawfully and only for supported workloads. You must not attempt, assist or enable any of the following:
- Malware, credential theft, phishing, exploitation, unauthorised access, scanning or denial-of-service activity.
- Spam, unsolicited bulk messaging, deceptive automation, platform manipulation or circumvention of rate limits.
- Cryptocurrency mining, proof-of-work, unauthorised proxies, relays, VPNs or unrelated distributed workloads.
- Child sexual abuse material, sexual exploitation, terrorist content or other unlawful content or conduct.
- Copyright, trademark, privacy, publicity or other third-party-rights infringement.
- Attempts to access other users, nodes, metadata services, internal networks, control planes or container infrastructure.
- Circumvention of account, resource, security, billing, suspension or technical restrictions.
- Excessive use of CPU, memory, storage, network, processes, builds or logs that threatens other users or the Service.
- Resale or commercial redistribution of Botkeep resources without written permission.
9. Moderation and enforcement
Botkeep uses technical security signals, resource monitoring and proportionate human review to investigate abuse. Authorised staff with a dedicated permission may manually request a read-only, AI-assisted source review for a documented security reason. The review inspects bounded excerpts of supported source files, applies static checks and may send redacted excerpts to Groq to identify possible capabilities relevant to section 8. It does not execute customer code, verify actual traffic, rank customers or decide whether an incident occurred. Comments, tool references and AI findings are not proof of a violation. Reports are advisory, may be incomplete or wrong, and require human verification; the feature cannot automatically ban, suspend, delete or change resources. No general pre-screening of every workload is performed. Provider, retention and data safeguards are described in the Privacy Policy.
Depending on severity, Botkeep may warn, rate-limit, stop, quarantine, restrict, suspend or delete a workload or account. Decisions must be diligent, objective and proportionate and must consider the rights and legitimate interests involved. Where required, an affected user will receive a clear statement of reasons and a route to request review. Advance notice may be omitted where urgent action is necessary for safety, security, evidence preservation or legal compliance.
Authorised staff may inspect the configuration, logs and relevant files or data only as necessary for requested support, maintenance, recovery, migration, security investigations, credible abuse notices, enforcement or legal duties. This is not an unrestricted right to browse private content or use it for unrelated purposes. Access is limited by staff permissions and the Privacy Policy; administrative actions are logged. Botkeep does not undertake general pre-screening of all hosted content.
10. Illegal-content and abuse notices
Anyone may submit a sufficiently precise notice through the permanent Report abuse page. A useful notice identifies the exact workload, account, URL or resource; explains why the information or conduct is allegedly illegal; identifies the relevant legal basis where possible; and provides contact details and a good-faith statement.
Botkeep will acknowledge and process complete notices in a timely, diligent, non-arbitrary and objective manner. Knowingly false or abusive notices may be rejected and may lead to proportionate restrictions. Information may be preserved or disclosed where required by law or a valid authority request.
11. Third-party services and software
Discord, GitHub, package registries, open-source packages and other connected services are controlled by their respective providers and have their own terms. Botkeep is not affiliated with or endorsed by Discord Inc. or GitHub, Inc. unless expressly stated. Changes, outages, suspensions or licence decisions made by a third party may affect the Service.
12. Backups, export and deletion
Keep independent copies of important code and data. Backups, where offered, are a recovery aid and not an archival guarantee unless a separate written agreement states otherwise. Deleting a workload or account may permanently delete associated files, configurations, deployments and logs after the applicable retention period.
Where mandatory law gives a consumer a right to retrieve eligible non-personal content, Botkeep will make the required export available subject to lawful exceptions and technical feasibility.
Only completed backups are recovery points. A failed or pending operation is not a backup. A restore can replace current files and database contents and may require the service to be stopped. Check the confirmation screen and keep an independent copy before a destructive operation.
Backup counts and advertised retention are shown for your plan. Automatic deletion solely because a backup reaches that advertised age is currently disabled; this is not a promise of indefinite storage or recovery. Customer deletion, server or account closure, lawful erasure and exceptional security measures remain separate. If automatic age-based expiry is introduced, the applicable schedule and advance notice will be provided before it affects existing backups.
13. Changes to the Service
Botkeep may patch or replace runtime versions, move workloads between nodes, adjust scheduling, restrict unsafe network behaviour, pause new provisioning or change operational features where reasonably necessary for security, legal compliance, software compatibility, infrastructure reliability, capacity or the sustainable operation of the service. Measures must be proportionate to the reason; a general reference to cost or capacity is not permission to disregard an agreed paid allocation or the Founder commitment.
Planned material changes will be explained before they take effect, with reasonable time to export or adapt where possible. Urgent security, infrastructure or legal action may require immediate intervention and subsequent notice where lawful. No change creates a new charge without agreement. Changes beyond what is needed to maintain conformity must satisfy applicable consumer-law conditions, including a valid reason, no additional cost and clear information.
Where a change has more than a minor negative effect on a consumer’s access or use and the digital-service modification rules apply, the consumer receives advance information on a durable medium and may terminate without charge within 30 days of the notice or the change, whichever is later, unless an unchanged conforming service remains available at no extra cost. Applicable refunds, remedies and content-retrieval rights are preserved.
14. Termination
You may stop using Botkeep and request account deletion at any time. Botkeep may suspend or terminate access for serious or repeated violations, fraud, security threats, legal obligations, prolonged inactivity or discontinuation of the Service. Where appropriate and legally required, notice and a reason will be provided.
Ordinary inactivity restrictions apply only under conditions disclosed for the relevant plan. Where safe and lawful, Botkeep will give a reason and a reasonable opportunity to remedy a breach or retrieve eligible data before permanent removal. Urgent risks, unlawful content, valid legal orders or the customer’s own deletion instruction may prevent that opportunity. A suspension is not an automatic right to keep the price of undelivered paid service; mandatory remedies remain available.
Termination does not erase information that must be retained for legal compliance, accounting, fraud prevention, security or dispute resolution. Personal-data retention is described in the Privacy Policy. Review of a restriction can be requested through support or the contact in section 20; serious or repeated abuse may justify refusing a later application, subject to law.
15. Paid services and consumer rights
Paid plans, when checkout is enabled, use single payments through the selected available provider, Stripe, Mollie or PayPal, not subscriptions. A purchase supplies 30 days from confirmed activation. Renewing the same plan before expiry adds 30 days to its existing expiry. When changing to another eligible higher plan during an active paid period, you choose either a new 30-day period at the displayed full plan price, replacing the previous expiry without carrying forward unused days, or an immediate upgrade for the proportional price difference over the remaining period, keeping the previous expiry. The choice, net price and duration are shown before order acceptance; applicable promotions are included in the quote. No automatic renewal or later off-session charge is authorised.
Catalogue prices exclude VAT. Stripe Checkout shows the applicable taxes and final total before payment. When Mollie or PayPal is available, Botkeep calculates applicable VAT locally and shows the net amount, tax treatment and total in the order summary before acceptance; the selected provider collects that fixed total. EU business reverse charge requires validation of the VAT number and associated company details; unsupported countries or special territories and conflicting location evidence may require Stripe or staff assistance. A zero tax amount is not itself proof of a general exemption. The order summary identifies the plan, resource pool and principal limits. A paid plan is assigned only after server-side payment confirmation; a return from the payment page alone is not confirmation. At expiry the account returns to its applicable free entitlement and existing resource-limit rules apply. Downgrades and non-upgrade plan changes are not offered during an active paid period.
Botkeep provides non-fiscal proformas and payment receipts in the panel. These are not tax invoices. You can request an invoice during checkout or contact the operator with your order reference and billing details; fiscal invoices are issued through the operator’s external invoicing process.
When crypto checkout is available, NOWPayments is an optional fourth provider. The order has a fixed EUR price, with applicable VAT calculated locally using supported reviewed rules; it does not expand fiscal coverage. NOWPayments displays the crypto amount, available coins and networks, minimums and any network costs on its hosted checkout. Send the requested amount using exactly the indicated coin, network and any required memo. Botkeep activates a plan only after verifying a complete payment with the provider; partial, mismatched, additional or late payments require staff review. Canceling the Botkeep order removes its checkout link but cannot cancel or reverse a blockchain transfer or invalidate an already copied deposit address. Do not send funds after cancellation or pay twice while a payment is being checked. Refunds are not automatic; contact the Operator for review under your applicable statutory rights. Botkeep does not request wallet seed phrases or private keys.
Payment documents and the order status are available to the customer in Billing and to authorised staff in the administration panel; this does not promise automatic delivery by email. Keep your billing details accurate. A price change applies to a later order only after its new total is shown and accepted; it does not authorise an extra charge for an already purchased period.
An unpaid, expired or cancelled checkout does not activate a plan. Refunds and chargebacks may require a review of the related entitlement and proportionate resource restrictions, but a payment dispute is not by itself proof of misconduct. Botkeep does not impose a blanket “no refunds” rule. Statutory remedies for non-supply or lack of conformity, including correction, price reduction or termination where applicable, remain available.
Consumers who have a statutory withdrawal right may notify [email protected] or write to Piazza Maria Montessori 11, 80011 Acerra (NA), Italy within 14 days after concluding the service contract, identifying the order and clearly stating their decision to withdraw. No special wording is required. The checkout separately requests express immediate activation; this is not a blanket waiver of withdrawal, conformity, remedy, refund or jurisdiction rights. Any amount due for service already supplied and any refund are assessed under applicable mandatory law. Contact the same address for payment disputes or a delayed activation.
16. Privacy and data protection
Botkeep processes personal data as described in the Privacy Policy. Where Botkeep processes personal data contained in a customer workload solely on the customer’s documented instructions, the Data Processing Addendum applies. These Terms do not replace either document.
17. Botkeep intellectual property
Botkeep and its licensors retain rights in the Botkeep name, branding, website, dashboard, documentation, interfaces and original software. While your account is active, you receive a limited, revocable, non-exclusive and non-transferable right to use the Service for its intended purpose. Mandatory reverse-engineering and interoperability rights are not restricted.
18. Warranties and liability
Free and beta features are supplied on an “as available” basis to the extent permitted by law. Nothing excludes liability for fraud, wilful misconduct, gross negligence, death or personal injury where liability cannot be excluded, mandatory conformity duties or other non-excludable rights. A lack of a contractual uptime guarantee does not eliminate those duties.
Botkeep is not responsible for a loss to the extent it is caused by the customer’s code, unsupported software, unauthorised configuration or third-party conduct and is not attributable to a breach by Botkeep. Independent backups reduce risk but do not exempt Botkeep from its own non-excludable responsibilities.
For customers acting exclusively for business purposes, and only where validly agreed, including any specific written approval required by law, aggregate contractual liability is limited to fees paid for the affected Botkeep service during the preceding 12 months. The exclusions above always prevail; this cap does not apply to consumers. This paragraph does not claim that merely browsing the site or ticking a general acceptance box fulfils a separate statutory approval requirement.
Events outside reasonable control may delay performance. Botkeep will take reasonable steps to mitigate their effects and communicate material disruption; force majeure does not override mandatory consumer remedies or excuse a failure to take measures required by law.
19. Governing law and disputes
These Terms are governed by Italian law, without prejudice to mandatory protections granted to consumers by the law of their country of residence. Consumer jurisdiction is determined by mandatory consumer law, including the court of the consumer’s residence where applicable. For users acting exclusively for business purposes, the courts for the Operator’s registered office have exclusive jurisdiction only where that choice is validly agreed with any specific approval required by law; otherwise ordinary jurisdiction rules apply.
Before formal proceedings, contact [email protected] or send a certified communication to [email protected]. An enforcement review may be requested through the same channels.
20. Updates and contacts
The current version is published at this permanent URL. Material changes will be communicated through the website, dashboard, email or another reasonable channel before taking effect, except where immediate application is required by law or an urgent security need.
This version is presented for new acceptances from its publication. Publishing a revision does not rewrite earlier acceptance records, grant consent on a customer’s behalf or retroactively change an existing paid order or individual Partner agreement. Where a new agreement or specific approval is required, Botkeep must obtain it. If a clause is invalid, mandatory law applies and the remaining valid clauses continue to operate.
General, privacy and appeal contact: [email protected]. Formal legal communications: [email protected].
21. Partner programme and sponsored plans
Partner hosting is an optional, selective sponsorship for approved projects and communities. Admission, resources, duration, review dates and any visibility or activity requirements are confirmed individually in writing. A conversation, application, displayed plan name or staff assignment does not by itself promise permanent sponsorship, a cash payment, ownership of resources or an exclusive business relationship.
Unless an individual agreement expressly guarantees a fixed allocation or period, complimentary Partner benefits are discretionary and may be reviewed, reduced, migrated, suspended or withdrawn for a reasonable, documented reason: an inactive or abandoned project; failure to meet agreed activity or visibility commitments; misleading information; unauthorised resale or diversion of sponsored resources; breach of these Terms; security or compatibility problems; insufficient capacity; or a material change in the programme’s operational or financial sustainability.
For a non-urgent change Botkeep will explain the reason and proposed timing, allowing a reasonable opportunity to respond, adapt or export data. Immediate action is reserved for the urgent circumstances described in sections 9 and 13. A review may be requested through the same support and legal contacts as other service decisions. A fixed-term or paid Partner commitment cannot be revoked merely by calling it discretionary.
Sponsored resources are for the approved project. Do not create extra Free accounts or combine free allocations to bypass the agreed Partner scope. Personal projects are allowed only within an applicable allocation and its normal rules. A Partner assignment does not automatically add the ordinary Free or Founder pool; any separate allocation must be expressly agreed.
At the end of sponsorship, continued hosting requires an available free entitlement that can accommodate the project or a paid plan you actively choose. No subscription, purchase or charge is created automatically. Unpaid sponsorship does not create a right to the cash value of unused resources, but this does not exclude mandatory compensation, refund or other rights. Publication of names, logos or partnership announcements requires the corresponding agreed permission; sponsorship is not permission to disclose private data.
22. Websites, databases and domains
Website and database hosting uses the same server slots and shared resource pool as applications. Domain registration, paid DNS, email mailboxes and certificates from a particular issuer are not included unless expressly offered. A Botkeep address or pretty alias is a service identifier, not a domain you own; it may be restricted or withdrawn for legal, security, abuse or necessary infrastructure reasons, with the safeguards in these Terms.
To attach a custom domain, you must control it, keep its DNS configuration correct and complete the requested verification. Botkeep may obtain and renew the necessary HTTPS certificate; public certificate-transparency systems may publish its domain name. A certificate secures the connection, not the content, availability or trustworthiness of your application.
You are responsible for your website’s content, visitor notices, cookies, lawful data collection, application security and database access permissions. A server-side file, query, restore or redeploy action can affect your data: check its scope before confirming. Use monitoring services only for targets you are entitled to monitor, and comply with third-party licences and service rules.
23. Integrations, invitations and promotional benefits
Discord and GitHub sign-in are optional. GitHub repository access is a separate optional integration limited to repositories you authorise. Importing or synchronising code requires the relevant rights; disconnecting an integration does not delete code already copied to your server or revoke credentials you embedded in that code. An import or deployment history is not a substitute for a backup.
Promotional plan codes, invitations and complimentary credits follow the eligibility, value and expiry disclosed for that offer. They are not cash, a transferable payment instrument or a promise that a paid credits store exists. A referral does not automatically earn a reward unless that reward was expressly offered. Botkeep may reject duplicate, fraudulent or quota-evading claims, with proportionate review; legitimate benefits remain subject to their confirmed terms.