You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added new section about benefits of publishing & monetization
Added details HTML component with hidden table
Mentioned briefly the available pricing model
Publishing your Actor on the Apify Store transforms your code into a sustainable revenue stream while eliminating traditional SaaS development overhead. When you publish your Actor, you automatically receive:
27
+
28
+
- A dedicated landing page showcasing your Actor's capabilities
29
+
- Built-in documentation hosting through README integration
30
+
- Direct exposure to organic user traffic
31
+
- Flexible sharing options with public or private source code settings
32
+
- Complete API documentation and integration examples
33
+
34
+
<details>
35
+
<summary>Publishing on Apify significantly streamlines the traditional SaaS development process</summary>
36
+
37
+
| Traditional SaaS Requirements | Handled by Apify Platform |
| Marketing campaigns | ✓ Store marketplace presence |
45
+
| Sales operations | ✓ Automated transactions |
46
+
47
+
</details>
48
+
49
+
**Monetization Options**
50
+
51
+
The platform supports various pricing models to match your Actor's value proposition:
52
+
53
+
- Fixed rental fee for continuous access
54
+
- Pay-per-result for usage-based pricing
55
+
- Event-based pricing for specific operations
56
+
- Custom pricing strategies for enterprise clients
57
+
24
58
## Maintain public Actors
25
59
26
60
While private Actors don't necessarily require ongoin maintenance, public Actors demand a highres level of resonsibility. Since public Actors are available on the [Apify Store](https://apify.com/store) and may be used by other users, an unmaintained public Actor could negatively impact those who depend on it.
@@ -39,7 +73,7 @@ If you decide to make your Actor's code publicly available on [GitHub](https://g
39
73
40
74
While refactoring and updating your Actor's code is encouraged, be cautious of making changes that could break the Actor for existing users. If you plan to introduce breaking change, please contact us at [[email protected]](mailto:[email protected]) beforehand, and we'll assist you in communicating the change to your users.
41
75
42
-
### Documentatino and testing
76
+
### Documentation and testing
43
77
44
78
Pay special attention to your Actor's documentation ([README](../../academy/get-most-of-actors/actor-readme)). It should be clear, detailed and readable, using simple language and avoiding technical jargon whenever possible, as your users may not be developers.
0 commit comments