Civo Write for Us

The Civo Write For Us program is an opportunity for members of the cloud-native community to share their expertise with the Civo audience. If your submission is accepted and published, you will be credited for your work and compensated for your contribution.

You can write about any topic that supports users on their cloud-native journey. This includes tutorials, walkthroughs, how-to guides, documentation, and in-depth overviews. Popular subjects often include Kubernetes, container technologies, storage solutions such as databases, machine learning, and networking. While detailed tutorials on emerging Kubernetes tools are especially popular with our audience, we welcome original ideas and unique perspectives beyond these areas.

Before writing your tutorial, you must submit your idea via the form at write@civo.com. You will be asked to provide your full name, email address, a short bio, the proposed title of your tutorial, examples of previously published work, and an outline or abstract with section headings. Our editorial team will review your submission and contact you by email to confirm whether your idea has been accepted.

Before writing your tutorial, you must submit your idea via the above form. You will be asked to provide your full name, email address, a short bio, the proposed title of your tutorial, examples of previously published work, and an outline or abstract with section headings. Our editorial team will review your submission and contact you by email to confirm whether your idea has been accepted.

No, we only accept original content. We cannot accept or pay for material that has been copied, paraphrased, translated, or generated from existing online sources, including AI tools. All submissions are checked using plagiarism and AI detection tools, as well as manual review, to ensure originality and quality.

All tutorials must be submitted as a Google Doc to allow our editorial team to make comments and suggestions directly within the document. Your tutorial must include both a title and a short snippet description.

The snippet is a brief summary used on certain pages and social media, and it does not appear within the body of the tutorial itself. You must structure your content using H2, H3, and H4 headings, and you should not use H1 headings, as these are reserved for the main title. In most cases, tutorials should include sections such as an Introduction, Prerequisites, and a Conclusion to ensure clarity and completeness.

Yes, images and screenshots are strongly encouraged. They help improve clarity, demonstrate expected results at each step, and make longer tutorials easier to follow. Any images used in your tutorial should be provided separately to the editorial team when you submit your draft so they can be uploaded alongside the published content.

If your tutorial includes code that is too long to display comfortably within the document, you may link to an externally hosted repository. Civo may choose to fork the repository into its official GitHub organization to ensure long-term availability. Any code referenced in your tutorial must be licensed appropriately for free and open use.

There is no fixed word count requirement. Your guide should be as long as necessary to explain the topic clearly and effectively, but it should avoid unnecessary repetition or filler content. We do not pay per word; instead, payment is based on the technical depth and effort involved in creating the tutorial.

Once you have completed your draft and checked it for spelling and grammar, you can share the Google Doc link with the editorial team. The team will review your submission and add any suggested changes or comments directly within the document. You will work collaboratively with the editors to refine the tutorial before publication. The review process typically takes up to two weeks, depending on the complexity of the piece and the technical input required.

All content created for the Write for Civo program becomes the sole and exclusive property of Civo. Civo reserves the right to edit, update, or remove content at any time. While you are encouraged to share and promote the published tutorial, you may not republish the content elsewhere, either in part or in full, without explicit written permission. You are permitted to share direct links to the content on the Civo website.

The fee for each tutorial is determined at the discretion of the Civo editorial team and will be agreed upon when your idea is initially accepted. Payment is made via PayPal or in Civo credit only, and no alternative payment methods are available. If the final submission does not meet quality standards, the provisional fee may be withdrawn.

Once your content is ready for publication and the fee has been agreed upon, payment is typically made within seven days, although it may take up to four weeks in some cases.

No, we cannot offer payment for content created before the Write for Civo program began or for content that was not approved in advance by a Civo content editor.

Yes, submissions may be rejected if they are not relevant to Civo users, if similar content already exists on the site, or if the topic does not align with current editorial priorities. If your submission is rejected, you are welcome to submit new ideas in the future.

We do not pay for tutorials written by authors representing commercial tools, applications, or open-source projects. In such cases, the opportunity is considered a co-marketing activity. If you are interested in exploring partnership opportunities, you can contact marketing@civo.com to discuss potential collaboration.