Frequently asked questions
Short answers for companies and partners who want to build on BusinessIntents: who owns what, how changes are made, what you may build yourself, and how you pay. Prices and plan details are on the Pricing page. Where this page and your Order differ, the Order and the Terms of Service apply.
The plans at a glance
| Standard | Dedicated | Builder | Factory | |
|---|---|---|---|---|
| Who owns the product | codbex | codbex | codbex | codbex; your rights are set in the contract |
| How the product changes | Settings and print layouts; new functions are built by us into the product | Same as Standard | Any standard module replaced by your own version, composed by us from your description | Without limits, by you or by us |
| Source code | No | No | No | Yes |
| Your own portal, desktop or mobile client through the API | Yes | Yes | Yes | Yes |
| What you pay for | Each user | Each user | Flat price, unlimited users | Annual contract |
Ownership and source code
Who owns BusinessIntents?
codbex. The modules, the platform, the interfaces and everything built into the product are the property of codbex on every plan. A subscription gives you the right to use the product, not ownership of it. Your data is yours; see Who owns the data?.
We asked for a function and paid for its development. Who owns it?
codbex. A function built into the product is part of the product, whether it entered our plan on its own or was built at your request and for a fee. What you pay for is having it built, and having it sooner. You use it under your subscription like every other function.
Can we get the source code?
On Factory, yes: the factory runs in your own cloud account and you have access to the source code. On Standard, Dedicated and Builder we do not provide the source code of the modules, the release process or the infrastructure.
Is BusinessIntents open source?
Not today. The application platform underneath, Eclipse Dirigible, is open source. We plan to publish some or all of the standard modules under the Apache License 2.0; there is no date yet, and until a module is published it is not open source. The release process and the operating infrastructure are not part of that plan; they are available with Factory.
Can we build and sell our own product from the BusinessIntents modules?
No. A copy, a derived version or a product under another name built from our modules is not allowed on Standard, Dedicated or Builder. On Factory, what you may do with what you build is set in the contract. What you build outside the product, connected through the API, is yours on every plan; see Can we build our own portal?.
New functions and changes
A function we need is missing. What can we do?
Tell us. There are three ways, depending on the function and the plan:
- It is of general interest. It enters our plan and is built into the product at no charge, at our priority. You get it with a regular update.
- You need it sooner, or it is specific to you. We build it for a fee, on an agreed date, and integrate it into the product.
- You want your own version of a module. That is Builder: any standard module is replaced by your version, composed from your description with AI assistance and tested in your own development and test environments before it reaches production.
On Factory you can make any change yourself.
Can we add our own module or our own code inside the product?
On Standard and Dedicated, no. Every customer on these plans runs the same standard modules, and code from outside is not built into them. On Builder your own version of a module replaces the standard one, and it is composed and released by us. On Factory you build what you need yourself.
Can a function be made available to an external system?
Yes. If you want to use a function from a system of your own, we expose it through the API as part of the agreed scope.
Building around the product
Does BusinessIntents have an API?
There is no public self-service API. When you want to connect a system of your own, we open API access to your environment for it: limited to your environment, with the rights of the users who work through it, and with a scope agreed in advance. Work on our side to expose a function is quoted separately. See Integrations.
Can we build our own portal connected to BusinessIntents?
Yes, on every plan. You build and run the portal, it carries your brand, and it is entirely your property. It reads and writes the data in your BusinessIntents environment through the API.
Is there a desktop application? Can we work offline?
BusinessIntents is a web application. There is no desktop client and we do not plan one for now. You may build your own desktop client for offline work and connect it through the API. Offline operation, local data, synchronisation and the resolution of conflicts are entirely your responsibility.
Is there a mobile application?
There is no native Android or iOS application. The web interface is adapted to small screens. A mobile application of your own is treated like a desktop client: allowed through the API, with synchronisation on your side.
How may we name and present an application we build?
Your application carries your name and your brand, and it is yours. BusinessIntents remains BusinessIntents:
- You may describe your application as working with BusinessIntents, for example "Xyz Desktop for BusinessIntents".
- You must tell your users that the business functions and the data behind your application are provided by BusinessIntents, a product of codbex, and that they need a BusinessIntents subscription.
- You may not present BusinessIntents, or its functions, as your own product.
- You may not use the BusinessIntents name or logo as the name of your product or company, or in a way that suggests your application is made or endorsed by codbex.
It is the same rule as everywhere in business software: whoever builds a client for another vendor's system owns the client, not the system.
If we build our own application, will you build the same thing later?
We may. Building an application around the product gives you ownership of your application, not exclusivity. Something we do not plan today can enter our plan later if enough customers need it. For example, we do not plan a desktop client now; if in six months most customers ask for one, we will build it. Your application stays yours and keeps working through the API. The same holds for a function built at your request: once it is in the product, it is available to every customer.
Can we read or write the database directly?
No. Access is through the API only, so that the accounting rules of the product apply to every change.
Who is responsible for what?
| Topic | codbex | You |
|---|---|---|
| Product core, accounting logic and reports | yes | |
| Hosting, updates, backups and security of BusinessIntents | yes | |
| Changes in legislation, within the product | yes | |
| The API: availability, compatibility and documentation of the agreed scope | yes | |
| Your portal, desktop or mobile client | yes | |
| Offline work, local data and synchronisation | yes | |
| Hosting and security of your applications | yes | |
| First-line support for the users of your applications | yes | |
| Prices and relationship with your own clients | yes |
On Factory the factory runs in your cloud account, and the split is agreed in the contract.
Payment
How do we pay when our users work through our own portal or client?
On Standard and Dedicated, each named person who can access the workspace needs a seat. Seats are purchased monthly in advance, whether the person works in BusinessIntents or through your portal or client. Builder has a flat monthly price with unlimited users. Factory terms are set in the contract.
Is the development of new functions included in the subscription?
Functions that enter our plan are included: you receive them with the regular updates. Development that you order, such as a function you need sooner, a function specific to you, or the exposure of a function through the API, is quoted separately. Builder includes four changes a month.
Taking part: who we work with and on what terms
BusinessIntents is one product with one owner. It is composed, tested and released by one team, so that every customer receives every update and codbex stays responsible for every result the product produces. For that reason there is no code from third parties inside the product, no marketplace of extensions and no listing of add-ons. There are three ways to take part:
- Bring and serve customers: accounting firms, resellers and implementation partners.
- Build your own application around the product, connected through the API: software companies and developers working for a customer.
- Contribute knowledge: domain experts, paid for their work.
| Role | What we need from you | What you get | How you earn |
|---|---|---|---|
| Accounting firm | Client companies that work in BusinessIntents | Less re-keying, clients' data in one product, no competition from us | Your own fees, set by you |
| Reseller or implementation partner | Customers, brought and looked after | A product that we keep current, without upgrade projects | Your own services |
| Software company | Your users working in BusinessIntents | Invoicing, payments, accounting and HR behind your product, without building them | Your own product, which stays yours |
| Domain expert | Your knowledge of the rules and of real cases | Paid work and early access | An agreed hourly rate |
| Developer | Contributions to the open-source platform underneath | An open project to contribute to today; the API through a customer; the modules, once they are published | Work for a customer |
I run an accounting firm. What do I get, and what can I do?
What we need from you. Client companies that do their daily work in BusinessIntents, and your judgement on where the product is wrong or incomplete for Bulgarian practice.
What you get.
- Your clients issue their invoices, record their purchases and payments and import their bank statements in the product, and the journal entries are prepared from those documents for your review. You check and post instead of re-keying.
- Each separately subscribed client has its own workspace and isolated data. See how companies are separated.
- Changes in legislation, within the product, are carried by us.
- codbex does not offer accounting or bookkeeping services, and does not ask you for exclusivity.
- Planned, not available yet: one profile from which a firm works with all its client companies. See the roadmap.
What you can do. Offer your accounting, payroll and advisory services at the prices you set; ask for functions your practice needs (how); build your own client portal through the API (how).
What you cannot do. Offer BusinessIntents as your own product, or change the modules.
Money. Your fees are yours; we take no part of them. Each client company has a BusinessIntents subscription at the published prices. Terms for a firm that brings and supports many client companies are agreed individually.
I resell or implement business software. What is in it for me?
What we need from you. Customers: companies you bring, set up and look after in their own language and market.
What you get.
- A product that we host, update and keep compliant. Your customers do not need upgrade projects, and you do not maintain a version of your own.
- The public demo on sample data, free and with no time limit, to show the product.
- Functions your customers miss are built by us into the product (how).
What you can do. Sell your own services: analysis of the customer's processes, configuration, preparation of data for migration, training and first-line support. Build your own applications for your customers through the API.
What you cannot do. Modify the modules, host the product yourself (except on Factory), or resell subscriptions without a partner agreement.
Money. You earn on your services, at your prices. The subscription is a contract between the customer company and codbex, at the published prices, unless a partner agreement says otherwise. Terms for partners who bring and support several customers are agreed individually.
We have our own software product. Can it work together with BusinessIntents?
Yes. This is the way to build on BusinessIntents without sharing ownership in either direction.
What we need from you. Your users doing their invoicing, payments, accounting, leave or payroll in BusinessIntents.
What you get. These functions behind your product without building and maintaining them, kept current by us. Any function you need from the outside is exposed through the API as part of the agreed scope (how).
What you can do. Build, brand, price and sell your product as you wish. It is entirely yours. It may be a web portal, a desktop client or a mobile application (details). It must say that it works with BusinessIntents (naming rules).
What you cannot do. Include our modules in your product, distribute them, or present BusinessIntents as your own.
What you do not get. Exclusivity: we may later build into the product something that your application does (details).
Money. Each company that uses BusinessIntents through your product has a subscription and pays per user, like every other customer (details). Work on our side to expose functions is quoted separately.
I am an accountant, payroll or tax specialist, or I know an industry well. Do you need me?
Yes. The product is only as correct as the knowledge behind it, and we would rather be told that something is wrong by an expert than by a tax inspection.
What we need from you. A review of how the product handles real cases in your field: which documents, postings, declarations and deadlines are right, which are wrong, and what is missing. Sample documents and forms. A clear verdict.
What you get.
- Paid work, at an agreed hourly rate, under a contract.
- Early access to what you reviewed.
- If you wish, your name as the reviewer of the area you covered.
- If you practise yourself: a product that fits the way you work, and the knowledge to offer your services on it before others.
What you do not get. Ownership of, or a share in, the product. Your conclusions are built into the product and become part of it.
How to start. Write to office@codbex.com with your field, your experience and the area you would review.
I am a developer. How can I take part?
Developers are welcome, and there are several real ways to take part. The one thing we do not offer is building extensions inside BusinessIntents and selling them: there is no marketplace and no share of revenue, because the modules are composed, tested and released by one team (why). We would rather say this at the start than have you find out later.
Where your skills are most useful.
- Contribute to the open-source platform underneath. BusinessIntents runs on Eclipse Dirigible, an open-source project at the Eclipse Foundation. It welcomes contributions today: issues, fixes, new features and documentation. What you improve there reaches BusinessIntents and every other product built on the platform, and your work is public under your own name.
- Build an application for a customer on that customer's API access: a portal, a desktop client, a mobile application or a connection to another system. The customer asks us for the access, and the application belongs to whoever you agree it belongs to (details).
- Work for a customer on Builder or Factory. On Factory the customer has the source code and may change it with its own or hired developers.
- Once the standard modules are published under the Apache License 2.0 (status): read them, run them, study them, report defects and propose corrections. The rules for contributions will be published together with the modules.
What we cannot offer. Access to the module source code before it is published, access to the release process, or payment from us for an application you build.
If you have an idea that does not fit any of these, write to office@codbex.com. We read every message.
What will stay the same, and what do you plan to change?
Stays the same.
- codbex owns the product.
- One team composes, tests and releases it, and there is no third-party code inside it.
- What you build outside, through the API, is yours, without exclusivity: we may build the same function into the product later.
- Standard and Dedicated use prepaid seats for named users.
- Accounting firms and partners set and keep their own fees.
- codbex does not offer accounting services.
Planned.
- Publishing some or all of the standard modules under the Apache License 2.0 (status).
- One profile for an accounting firm across its client companies.
- Opening API access without waiting for the team.
See the product roadmap for available features and planned additions.
We serve many companies. How are they separated?
Each separately subscribed client has its own workspace, with its own records and access settings. Standard workspaces run on a shared instance and each has an isolated schema in a shared database. Dedicated runs on its own instance and database.
Can we offer BusinessIntents under our own name?
Not as your own product. The applications you build around it, such as a client portal, carry your brand, and must say that they work with BusinessIntents; see how to name and present an application. On Dedicated and above the product runs on your own domain.
Data
Who owns the data?
The company that entered it. You can export lists and reports to CSV while you have access. After the subscription ends, the applicable terms govern access and export. See Data Hosting.
Still have a question?
Write to office@codbex.com with your company name and what you want to build.