Cockpit Project icon
Cockpit Project icon

Cockpit Project

Makes it easy to administer Linux servers via a web browser. It allows you to easily perform simple tasks like storage administration, inspecting journals, starting & stopping services, monitoring & administering several servers at once.

Login View

Cost / License

Application type

Platforms

  • Linux  [https://github.com/cockpit-project/cockpit/blob/master/HACKING.md](https://github.com/cockpit-project/cockpit/blob/master/HACKING.md)
  • Flathub
  • Self-Hosted
44likes
0articles
Save

Features

Properties

Features

Highlights All activities

Cockpit Project News & Activities

Recent News

No news, maybe you know any news worth sharing?

Share a News Tip

Recent activities

Cockpit Project information

AlternativeTo Categories

Network & Admin, OS & Utilities, System & Hardware, Development

GitHub repository

  •  15,243 Stars
  •  1,364 Forks
  •  495 Open Issues
  •   Updated  
View on GitHub

Our users have written 1 comments and reviews about Cockpit Project, and it has gotten 44 likes

Cockpit Project was added to AlternativeTo by rotexdegba on and this page was last updated . Cockpit Project is sometimes referred to as Cockpit, Cockpit Linux. 

Comments and Reviews

   
matt g
0

my first VPS and Cockpit Project seems like a very clean, straight-forward server managing program. best of all, it's Free & Open Source!

Featured in Lists

Selfhosting

Selfhosting is where you're hosting your own websites, apps, software, tools, and much more on your own server instead of having to rely on 3rd-party cloud providers such as Hetzner. Taking this approach to hosting gives you more control over your data and how your server or servers are managed. When you are running multiple things on one or two servers, within your home, it's called a "Homelab" and you're "Homelabbing" at that point. Running your own server and homelab within your home is great for privacy-conscious individuals such as myself, tech enthusiasts, small businesses, and those seeking more control of their digital life. The following lists provided here are applications and software I've gotten comfortable with and enjoyed using over the past 3 and a half years since I started homelabbing, it's based on my experience and what fits my criteria. Some well known softwares won't be listed here, as my experience may of not been at best with them. My criteria is that software is built in the open, respects user privacy and security, should not require a license to operate, and don't contain profanity and other minor things. I'm also willing to test new software to selfhost, feel free to comment or message me to try out other alternatives. There are other places to check out as well for those interesting selfhosting, such as Awesome Selfhosted, selfh.st, and other places you can find on the internet. https://github.com/awesome-selfhosted/awesome-selfhosted https://github.com/awesome-foss/awesome-sysadmin https://github.com/veggiemonk/awesome-docker If you ever need help with selfhosting, you can check out the following communities: Homelab Community on Fluxer, I personally run /r/selfhosted (Reddit) /c/selfhosted (Lemmy / Fediverse) There's also a wiki you can look into as well. If you believe an alternative software should be added to this list, please contact me or direct message via my AlternativeTo account. I'm also available on Signal. This lists gets updated every month at least, check back regularly.
By Korbs81 appsUpdated

Open-Source Slopware

A list of open-source software containing slop (LLM generated) code or endorses the usage of LLMs in other ways. This list contains software that obviously accepts irresponsible coding practices or promotes LLM usage. I found these applications while searching for alternatives to previously used software that turned out to contain code generated by slop-machines. Each of added applications have at least one link that points to the verifiable proof. This list by no means is meant to cover all the software that contains code by not-so-intelligent tools and people using them but to serve as a reminder to myself about what I have already checked. Why having LLM generated code (and using generative tools in general) is bad? Ethical reasons — such as illegally retrieved training material, underpaid workers that prepare the training data. Impact on environment — increased fossil fuel usage to supply the needed electricity power, water usage in water scarce regions. This somewhat overlaps with the above. Social impact – noise pollution in neighbourhoods near AI data centres, air pollution from diesel- or gas-powered turbines (also overlaps with the above), resource consumption by data centres drastically increases utility prices. Impact on brain and thinking, reasoning — by offloading thinking and decision making to machines people are shooting in their foot (more like in their head) as this leads to brain rot. Less intelligent people are easier to control. Even legal issues (especially in open-source software as it cannot be guaranteed that the “generated” code is not really just re-used, thus unknowingly violating the source license). Inevitable enshittification — every software product from big technology eventually gets enshittified to maximize revenue. For users this could mean hidden or plain ads, biased opinions/information, privacy violations, increased prices for LLM based tools. Burden on open-source software maintenance — LLM tools provide easier access to code contributions which often shifts the responsibility of checking code quality from developers to maintainers and reviewers. Digging through walls of merge request text and code generated by slop-machines takes valuable time that otherwise could be spent more meaningfully by fixing bugs and working on new features. I will try to add links that back up the claims above, but it may take a while. Of course, I see how and where generative tools could be helpful and sometimes I feel tempted to find an acceptable way to use them, but for now the direct and indirect costs far too much outweigh gains. This list has its positive counterpart: Slop-Free (Supposedly) Open-Source Software (not quite complete yet). Also take a look at and give thumbs up to AI Slopfree Software Catalog which contains software dedicated against usage of LLMs. Also, here is a list of some labels that can be added / voted for so they would eventually appear on application pages: Slopware; Slop (LLM) Code; Slop-Source Software; Open-Source Slopware; Contains Slop (LLM Generated) Code.
By Edgars172 appsUpdated

WebUI Control Panel`s for your home server

For easier control off your home server. Here is a list off webUI Control Panels for just that.
By NinjaHow7 appsUpdated

Official Links

Install from the command line

  • flatpak install flathub org.cockpit_project.CockpitClient

Be careful what you paste into a terminal. Check what a command installs before running it.

What is Cockpit Project?

Thanks to Cockpit intentionally using system APIs and commands, a whole team of admins can manage a system in the way they prefer, including the command line and utilities right alongside Cockpit.

Simple to use

Cockpit makes Linux discoverable. You don’t have to remember commands at a command-line.

See your server in a web browser and perform system tasks with a mouse. It’s easy to start containers, administer storage, configure networks, and inspect logs. Basically, you can think of Cockpit like a graphical “desktop interface”, but for individual servers.

Compatible with your existing workflows

Have a favorite app or command line tool that you use on your servers? Keep using the command line, Ansible, and your other favorite tools and add Cockpit to the mix with no issues.

Cockpit uses the same system tooling you would use from the command line. You can switch back and forth between Cockpit and whatever else you like. Cockpit even has a built-in terminal, which is useful when you connect from a non-Linux device.

Integrated

Cockpit uses APIs that already exist on the system. It doesn’t reinvent subsystems or add a layer of its own tooling.

By default, Cockpit uses your system’s normal user logins and privileges. Network-wide logins are also supported through single-sign-on and other authentication techniques.

Cockpit itself doesn’t eat resources or even run in the background when you’re not using it. It runs on demand, thanks to systemd socket activation.

Extendable

Cockpit also supports a large list of optional and third-party applications.