Source code management

Experience fast and scalable hosting for private, Git-based repositories with a web-based interface to browse and edit code plus flexible rules for granting member access.

Online code browsing

Browse commits and files by change author, branch, or filename. Review the change history and annotations from other developers. Toggle the appearance of side-by-side diffs and discussions to gain insight into what changed and why.

Edit files and commit changes

Make minor changes directly in the web-UI, without switching to a dedicated code editor.

Monitor commit status from external build servers

Merge and move on with confidence by tracking whether changes committed to the codebase result in success or failure when built by a connected CI server. Space integrates with TeamCity (available), GitHub Actions, or Jenkins (planned) and can retrieve status codes, branch details, timestamps, and more.

Manage and protect your source code

With Space, you have a choice of integrated security feature support that allows you the maximum flexibility to safely and securely control access to your source code.

Push restrictions

Configurable push restrictions make collaboration on the source code clear, transparent, and secure.

Protected branches

Set up rules for working with branches using a granular permission scheme.

Mirroring

Mirror your repository from GitHub with two-way synchronization. Invite commits from external collaborators while keeping your development secure in Space.

Regional replication planned

Working in a distributed team? Use regional replication to provide faster access to your repositories from various geographical locations.

Code review

Establish a robust, customizable, and integrated code review process that works for you no matter whether you want formal rules and conditions or not. Review code in the branch before it’s merged to master, or after merging one or more commits. Space supports both workflows with ease.

Collaborate on code in place

Start discussions and collaborate with your teammates directly inside the codebase. Contributors can reply directly or react with emoji. In the end, your code remains easy to read, debug, maintain, and extend. The messy conversations are safely contained inside the vacuum of Space.

Efficient and effective code reviews

Track discussions between the reviewer and the author with a transparent system for accepting changes and resolving concerns.

Review commits and enter comments as you go through each file before collaborating with the author, who can update the code and leave a reply or resolve the discussion.

Merge requests

You can restrict direct commits to the master (or any) branch using the permission scheme. Create merge requests that are accepted automatically after automation tests have passed or when a code review that follows a predefined flow is complete.

Set your rules

A successfully finished automation job, approval from a designated teammate, a check provided by an external service — any combination of these conditions can serve as a quality gate that must be passed before users can merge their changes.

Integration with IntelliJ-based IDEs

Connect IntelliJ IDEA or any other IntelliJ-based IDE to Space to get access to your repositories, code reviews, Automation (CI builds), and packages. The Space plugin is bundled in IntelliJ IDEA 2021.1, and you can install the plugin manually in our other IntelliJ-based IDEs.

With the Space IDE plugin you can:

Clone Space Git project repositories right from your IDE.
Perform code reviews with merge requests and discuss code snippets with your teammates right from your IDE.
Easily edit Space automation scripts in IntelliJ IDEA with code highlighting and automatic code completion.
Resolve missing Space package references directly in the IDE. planned

Automation

Modern and intuitive ways to organize your continuous delivery pipelines along with a solution for a broad spectrum of automation tasks.

Continuous Integration and Continuous Delivery (CI/CD)

Simple yet powerful CI/CD out of the box: on-the-fly test reporting, parallel execution, local reproducibility (planned), with coverage for major technical stacks like Gradle and Docker.

Automation workflows planned

The Automation module can pull data from any other module in Space, including issues, version control, teams, and chats. Moreover, Space modules generate events (a new code review, a new issue, or a new member creation), which can then trigger specific automation scripts.
For example, you can run an automation script that sends a welcome email with valuable information to a newly added member in Space or create a task for the IT team to set up a workspace.

Configuration as code

Automation in Space is configured using scripts. The Automation UI in Space is used to visualize script results: logs, tests, and artifacts. Space uses a Kotlin-based DSL as its scripting language, with plans to support YAML in the future.

Integrate with other Space modules

In an Automation script, you have access to the Space HTTP API client. This lets you work with any other Space module: send messages to Chats, create articles, access team directory, and much more.

Containers, VMs, and functions

Space can execute automation in a range of environments:

Run pure Docker images from Docker Hub or your Space image repository.
Support for Linux, Windows, and macOS virtual machines. planned
Support for serverless functions. planned

Integrate with external tools

Get access to an assortment of APIs that connect to external tools and services, including:

api.docker: to build and publish Docker images.
api.gradle: to build and report tests using Gradle.

In the future, we plan to extend this list to include .NET, npm, Maven, Bazel, and others.

Local reproducibility planned

Run automation scripts locally to test them before pushing to the Space server, using either:

The Space plugin for IntelliJ IDEA, which lets you run scripts locally and provides automatic code completion and code inspection.
The Space Automation command-line tool.

Package management

Create and use package repositories in your CI/CD pipelines or from your local machine. Share packages between products using Container, Maven, NuGet, and npm repositories.

Apps distribution

Use container registries to distribute your apps as container images, and use them during deployment.

Package dependencies

Use a local repository (ready) to store and consume packages privately and mirror repository (planned) to mirror an upstream repository, like Maven Central or nuget.org, to keep the required package dependencies as long as you need them.

Powerful search

Find and view package details to understand how it was produced.

Package vulnerability analysis planned

Configure Space to check packages against common vulnerability issues automatically. These checks can be especially helpful before publishing a package to production.

Software Development