Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
How Do I Reset My Password?
How to reset your Code Capsules account password using the dashboard.
How Do I Enable 2FA?
How to enable two-factor authentication on your Code Capsules account.
To reset the password for your Code Capsules account:
Navigate to the Account tab in the dashboard.
In the Security section, click Change Password.

Code Capsules uses an hourly billing model, so you only pay for what you use.
Capsule pricing starts at $3/month on the Basic plan and increases as you scale CPU, RAM, or replicas.
To customize resources, select Custom when creating a Capsule.

Teams, Spaces, and Capsules form the foundation of Code Capsules.
A Team is a group of developers who share access to the same Spaces and Capsules for easy collaboration.
Each Team is linked to a payment method, and the associated credit card is billed when charges are incurred.

Code Capsules accepts Visa and Mastercard.
To add a card to your account, click Billing in the top navigation bar, then click Add.
Enter your card details and click Confirm Payment Method.


Teams, Spaces, and Capsules form the foundation of Code Capsules.
A Space is an organizational tool for managing Capsules. Each Space can contain multiple Capsules, making it easier to structure and manage large or complex projects by grouping related Capsules together.
You can create as many teams as you need on Code Capsules.
To add a new Team, click the yellow + button in the bottom-left corner of the dashboard and select New Team.
Give your Team a name and click I Like It! to confirm.
To remove a Team, go to the Details tab in the Team dashboard and select Remove Team.
You'll need to from the Team before it can be deleted.
Protect public-facing URLs on your Capsule with HTTP Basic authentication.
Navigate to the Domains tab and scroll down to the Basic Auth section. Toggle Basic Http authentication to Enabled to secure your Capsule with a username and password.
When HTTP Basic authentication is enabled, your username and password will appear in the Basic auth credentials section. Click show to view the username and password needed to access the protected Capsule.
Change your billing details in the Billing tab in the Code Capsules dashboard.
Click Edit in the Billing Details section, make the necessary changes, then click Save.
Once you've created a Team, invite members to join.
Click + (Add Member), add members' email addresses in the text field, and click Invite Team Members to send the invitation.
Your Team is now ready to collaborate.
, , and Capsules form the foundation of .
Capsules provide the computational power to run your applications.
While Teams and Spaces are organizational tools, Capsules are where the actual build and deployment happen. They connect to your GitHub repositories and host your applications. Capsules can run both frontend and backend applications.
When a Capsule is created, it automatically builds and deploys. You can monitor the build process by:
Navigating to the Logs tab, or
If you've already , you can share access to your repos with your Teams.
Click Share repositories with Team, toggle on the repos to share with your Team, then click Share Repos.
Clicking View build log under the Build and Deploy tab
When a Capsule is deployed, an HTTPS subdomain is generated for it. Find the subdomain in the Config tab. Click the subdomain to open the link in a new tab.
Turn off a Capsule by toggling the switch at the top right of the Capsule Details view (next to Live Website).









To create a new Space, click the yellow + icon on the bottom-left corner of the dashboard and select New Space.
Choose the Team to add the Space to.
Give the Space a name.
Select your location.
Click Create Space to finish.
To remove a Space, go to the Details tab in the Space dashboard and select Remove Space.
You'll need to from the Space before it can be deleted.
Code Capsules is a comprehensive platform-as-a-service (PaaS) that streamlines software development.
Particularly well-suited to developers using , Code Capsules brings together backend, frontend, and database services in a single platform.
Use Code Capsules to eliminate the need for separate tools like Heroku, Netlify, and Atlas and simplify your development workflow.
To view your invoices, go to the Invoices tab in the Code Capsules dashboard.
An all-in-one solution for managing frontend, backend, and database services from a single platform, simplifying application setup and maintenance.
Push your code to GitHub and quickly have it running in a cloud production environment – reducing deployment time and complexity.
Real-time collaboration and team management tools make it easy to coordinate efforts and maintain transparency throughout the development process.
Automates repetitive tasks with continuous integration and deployment (CI/CD), making it easy to iterate and deploy updates without downtime.
Customizable resource allocation for easy scaling and built-in data-management tools make the platform suitable for everything from small projects to enterprise applications.
Supports a wide range of programming languages and frameworks, offering the flexibility to use your preferred tools, support diverse tech stacks, and scale without switching platforms.
Includes performance management, built-in security, and real-time issue detection to keep your applications running smoothly and securely.
With a free tier available and paid plans starting from just $5 per month, Code Capsules is an affordable option for startups and small businesses looking to minimize costs without compromising on functionality.



To set up two-factor authentication (2FA) for your Code Capsules account:
Navigate to the Account tab in your dashboard.
In the Security section, click Enable 2FA.
Teams, Spaces, and Capsules are the foundation of Code Capsules.
Teams are to organize people. Multiple people can join your Team, and each member of the Team can interact with the Spaces and Capsules that the Team contains. Furthermore, Teams are associated with a payment method – you add a credit card to a Team, and Code Capsules bills this credit card when a charge incurs.
Spaces are the second layer of organization. Spaces can contain any amount of Capsules and are excellent tools for larger projects. If your project involves complicated frontend and backend code, splitting your code into multiple Capsules – each within the same space – may help with organization.
Capsules provide the actual computational power for running your applications. While Teams and Spaces are organizational tools, Capsules connect to GitHub repositories containing your applications and hosts them on a server. Capsules can run both frontend and backend applications.
For a single, simple project, you would have exactly one team, containing one space, containing one capsule. If you wanted to set up a frontend only project (e.g. a React app) backed by a REST API, you would have two capsules in your space: a frontend Capsule for the React application and a backend Capsule for the REST API.
When creating a Space, you’ll be prompted to choose a deployment location. All Capsules in that Space will be deployed to the selected location.
Code Capsules offers several physical cloud data centers. We recommend selecting the location closest to your target users:
South Africa (Cape Town)
Europe (North)
United Kingdom (South)
To deploy applications on Code Capsules, you need to connect to a version control provider and give Code Capsules permission to read the relevant repository.
To connect your Code Capsules account to your version control provider, navigate to Repos in the dashboard and click Install next to your preferred provider.
Follow the prompts to give Code Capsules access to your repos.
For example, to connect to GitHub, select your GitHub username and set the following options in the dialog:
Enable Only Select Repositories.




Select the GitHub repository you want to deploy from.
Click Install & Authorize.
Once version control is connected, you can share repos with your Teams.

Improved builds UI, we now include time the build took as well as branch and commit hash details
Successful automatic builds have a link to the git commits diff between previous and current build
New deployment strategy configuration, select between rolling update or re-create (forces the new instance regardless of the previous builds instance shutting down)
Improved metrics accuracy as well as graphs for multiple replicas across capsule types
Private enterprise customers: GPU flag to ensure your workloads consume GPU compute
Performance improvements to egress networking
General bug fixes and improvements across the site
New agent capsule type:
Improvements to Postgres data capsule horizontal scaling
Capsules shouldn't rebuild on certain config changes like port and environment variables, it will just restart the capsule
Improvements to instance restarts, previously duplicate restarts occurred
Our new CLI has been released. Check it out .
Ability to proxy and connect to your deployed workloads via the cli, allowing you to debug services or access your databases from your local machine
Fixed a bug when trying to scale storage down (this is not possible)
Fixed a bug when trying to scale databases horizontally, the correct replicas are created without any issues
New and improved alerting. Check it out .
Ability to get email notifications for any workload alerts like OOM, too much CPU being used, unexpected app crashes, etc.
Performance improvements
Bug fixes
We’ve rolled out some big updates across logging, storage, monitoring, and scaling.
Here’s what’s new:
Logging Overhaul: Logging just got a whole lot smoother
Brand new logging UI with a cleaner experience.
Filter logs by replica/instance for horizontally scaled workloads.
Blazing fast querying & searching.
Real-time logs via websockets (no more delayed polling).
For Internal Developer Platform (IDP) customers:
Improved backend performance & stability → lowers infra costs while boosting performance.
Updated dependencies and security patches across the logging stack.
Smarter handling of storage and database workloads.
Automatic self-healing for horizontally scaled workloads during restarts.
Helps right-size infrastructure for lower costs and better performance.
Laying the groundwork for websocket-based capsule state management.
Coming soon: real-time capsule status updates (starting, running, scaling, shutting down, OOM, etc).
Enhanced monitoring stack with advanced alerting and integrations.
Custom dashboards & reporting across infra, platform, and applications.
Support for custom metrics scraping/importing.
Flexible backup schedules: daily, weekly, or monthly.
Supported across Storage, MySQL, Postgres, and Mongo.
Scale CPU and RAM independently to fine-tune workload requirements.
(e.g. high CPU + low RAM or the other way around).
That’s it for now, with these updates, you’ll see faster insights, better reliability, and more flexibility across your workloads.

Date/time filters with improved performance for historical digging.
Download logs in JSON, text, or CSV.
Full-screen mode for easier reading.
Beta: Log retention by time and size.
Configure the Capsule's resources by choosing a plan. To customize resources to suit your needs, select Custom and move the sliders to increase or decrease CPU, RAM, and Replica Scale. Click Next.
Code Capsules connects to your version control provider to deploy applications from your repositories. You need to give Code Capsules permission to access the repository you want to use.
To connect a Capsule to your repository:
Select the repository from the dropdown. If you haven't yet linked your Code Capsules account to a version control provider, click Configure Git for Code Capsules and follow the prompts.
Select the branch to deploy from.
Select the folder the Capsule will build from, or leave this field blank to build from the root of the branch.
Capsule-specific settings depend on the type of Capsule you're creating. For example, if you're adding a Frontend Capsule, you'll specify a build command, the path to the project's static files, and a name.
Click Create Capsule to complete the setup.
To delete a Capsule, navigate to the Capsule Details page, scroll to the end, and click Remove Capsule.
In the confirmation dialog, enter the Capsule's name and click Delete.
You cannot reverse this action. The Capsule cannot be recovered once deleted.
To turn off a Capsule, toggle the switch at the top-right corner of the Capsule Details page.
Turning a Capsule off is useful when adding or updating environment variables. You’ll need to restart the Capsule after a few seconds for the changes to take effect.
You can also turn off a Capsule during periods of inactivity to reduce costs.







Each application deployed on Code Capsules is assigned a default domain in the format capsulename.xxxx.codecapsules.co.za.
At no additional cost, you can configure Code Capsules to use a custom domain you own (like example.com) instead of the default domain.
The Domains tab contains all information about a Capsule's domain, including the option to add a custom domain.
To add a new custom domain, click the yellow + button in the top-right corner of the dashboard.
Copy and save the Static IP address.
Click the Add Custom Domain link and enter your custom domain in the Domain Name field.
Ensure you enter only a root domain. Do not include a subdomain. A root domain contains only a domain name and top-level domain, for example, example.com. See the below.
Click Create Domain.
Next, you need to create an A record with your domain registrar for the custom domain you've purchased.
Log in to your domain registrar's dashboard and locate the DNS settings for your custom domain.
Retrieve the static IP address you and add an A record pointing to it. Your A record entry may look something like this:
Where:
@ refers to your root domain (for example, example.com).
provided-IP-Address is the static IP address from Code Capsules.
Consult your domain registrar's documentation for specific instructions on adding A records to your domain.
Before adding a subdomain, make sure your custom domain has an pointing to your application on Code Capsules.
To add a new subdomain, click the yellow + button in the top-right corner of the dashboard.
Click the Add Custom Domain link and enter the subdomain to create in the Domain Name field.
Click Create Domain.
Next, you need to create a CNAME record with your domain registrar for the subdomain you added.
Log in to your registrar's dashboard and navigate to the DNS settings for your domain. Add a CNAME record for the subdomain. Your CNAME record entry may look something like this:
Where:
subdomain is the subdomain you're adding, for example, app or www.
your-root-domain is your root domain that contains an A record routing to your application on Code Capsules.
Consult your domain registrar's documentation for specific instructions on adding CNAME records to your domain.
To remove a domain or subdomain from a Capsule, go to the Capsule's Domains tab.
All associated domains and subdomains are listed in the right-hand panel. To remove one, click the trash can icon next to the domain or subdomain.
Removing a custom domain or subdomain does not update or delete its DNS records.
If you remove a root domain, update the A record with your domain registrar to remove or change the IP address.
If you remove a subdomain, delete the corresponding CNAME record from your DNS settings.
Uniform Resource Locator (URL): A web address used to locate a resource on the internet. URLs typically include a subdomain, a second-level domain, and a top-level domain.
Subdomain: The portion of a URL before the main domain name, most commonly www. Subdomains are often used to organize different services or sections of a website (for example, hr.myapplication.com might route users to your company’s human resources portal).
Second-level domain (SLD): The core name of the domain, located between the subdomain and the TLD. In www.example.com
Domain Registrar: A company that sells and manages domains.
A Record: Routes a domain (for example, example.com) to an IP address (for example, 123.456.567.8).
Wildcard Subdomain: Routes all undefined subdomains of a domain to a specific destination. For example, if the *.example.com wildcard subdomain points to example.com
Hypertext Transfer Protocol (HTTP): Protocol used to transfer data from a server (such as a web application) to a client (such as your web browser).
Hypertext Transfer Protocol Secure (HTTPS): A secure version of HTTP that encrypts data transferred between the server and client for better security.
Secure Sockets Layer (SSL) Certificate: Authenticates a domain and enables encrypted communication between a server and a client via HTTPS (for example, https://www.example.com).
exampleTop-level domain (TLD): The final part of the domain name, such as .com, .org, or .co.za. TLDs often indicate the purpose or location of a website, for example, .de typically signals a website based in Germany, while .org is commonly used by non-profit organizations.
Root Domain: The combination of the SLD and TLD, excluding any subdomains, for example, example.com.
info.example.com123.example.comexample.comCNAME Record: Also known as an "alias", routes a subdomain to another domain name (for example, mail.example.com -> mail.google.com). Unlike A records, which point to IP addresses, CNAME records point to domain names.
A Record
@
provided-IP-Address
CNAME
subdomain
your-root-domain


