A Parrot Security environment for careful research and authorised testing. Bring project tools, development work and lab evidence into a Swiss KVM workspace configured around your assessment.
A smaller Parrot Security configuration for learning, utilities and targeted authorized assessments. Two vCPUs, 2 GB of DDR4 memory and a 30 GB SSD keep the resource allocation focused.
A Parrot Security environment for authorized research and development, with 5 Xeon 5600 vCPUs, 2 GB of DDR4 memory and a 45 GB SSD. The traffic allowance is 3 TB.
A Parrot workspace with 8 vCPUs and 4 GB of DDR4 memory for maintaining several tools or development tasks. It includes 60 GB of SSD storage and 5 TB of traffic.
The largest Parrot allocation offers 12 vCPUs, 8 GB of DDR4 memory and a 100 GB SSD for more substantial authorized research workloads, with a 300 Mbps port and 10 TB of traffic.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
Build the workspace around the Parrot Security environment, with your project utilities and a workflow appropriate to the systems you are authorised to assess.
GUI and VNC options let you select a desktop workflow where needed. Administration access remains something to configure and secure deliberately.
Compare the listed CPU, RAM and SSD resources. Add capacity based on the tools and material involved in the work, rather than the plan number.
Review additional IPv4, port-speed and daily-backup choices. Keep data movement and evidence retention consistent with the approved project.
Study your own application behaviour and evaluate security tools in a separate environment with controlled access.
Maintain a project workspace for assessments whose targets, permissions and evidence-handling requirements are documented.
Prepare and test utilities against your own lab systems before using them in an approved assessment.
Parrot and Kali are different starting points for security work. Choose the environment that suits your team's tooling, package requirements and habits. The name of a distribution is not a substitute for verifying that the applications and versions you require are present and maintained.
Separate project files, remove expired access and clean up temporary material when an assessment ends. A research workspace may hold customer information, so use appropriate access restrictions and retention rules. These controls matter as much as the Swiss location of the server.
The Parrot range contains different combinations of CPU, memory, disk and network capacity. Compare the actual table rather than assuming that a higher numbered plan always suits a larger workload. GUI, backup and network additions are separate choices that should be reviewed before confirming the configuration.
Define the packages and versions needed for your research before choosing the environment. Confirm the Parrot image, root access and SSH credentials at delivery; a GUI and VNC are separate choices. The base specifications list Layer 3–4 protection. Console recovery, a custom image and changes to an existing workstation require operator confirmation, while project authorisation remains yours to establish.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
No. They are different distributions. Select based on the tools and workflow your project needs, and compare the listed resources independently.
Use the CPU, memory, disk and traffic specifications to compare them. Plan names are identifiers and should not be treated as a resource ranking.
Check the selected GUI option in the configurator. A graphical interface is a distinct choice, and VNC has its own selection.
Systems you own or targets for which you have explicit permission within an agreed scope. The server location does not change that requirement.
Restrict access, protect credentials and choose a defined retention period. Treat automatic backups and exported evidence as part of the same confidential project.
Confirm the delivered toolset against the requirements of your project. A distribution name does not guarantee every package, version or specialist application is installed.
Plan a protected SSH administration path and confirm root credentials at delivery. GUI and VNC selections are separate from command-line access and need their own secure access rules.
Yes. The base specifications list Layer 3–4 protection. The advanced paid selection is separate; it does not define the privacy of commands, evidence or application data.
CPU, RAM, disk and network options are visible in the catalogue. Confirm the actual upgrade procedure, stock and any interruption before changing a delivered workstation.
Choose your resources. Keep control of your identity.