Platforms
Web applications for the working day: clocking and hours, equipment inventory, and control of who uses what. The data stays in your system, roles are clear, and the product speaks Portuguese and English when the work crosses a border.
Licensing and operations.
Mail and folders on the device.
From the office to the phone.
CodeSharper Solutions designs web platforms, licensing, Android apps, AI training and the agents the team will use.
WHAT WE DO
Platforms for clocking, hours and inventory. Licensing from the sale through to the audit. Android apps with mail, conversations and folders on the device. Installation of the next version. Artificial intelligence training for the team. Agents with one task and a trace of what they did.
Web applications for the working day: clocking and hours, equipment inventory, and control of who uses what. The data stays in your system, roles are clear, and the product speaks Portuguese and English when the work crosses a border.
The sale, the renewal, the reseller and the client in one place. Trials, unlock requests, commissions and audit. Anyone entering the web confirms their identity. When the software asks, the platform answers.
Phone apps held to the same standard as the desktop. Mail that stays on the device, closed conversations, folders with encryption, agreements between companies, and a work session followed from the phone.
A signed installer and an update on top of the previous version. The program opens under the same name. Installation includes the licence and the first account.
We train the team on their real work. How to give an instruction that can be checked, how to review what the agent returns, and when the decision stays with the person. Training ends when people are using what was installed.
Each agent does one concrete task: it reads, decides and writes in the right place, and leaves a trace of what it did. It keeps a memory of the work, uses limited tools, and has a person accountable for the result.
SYSTEMS
cGrant records the licence, the sale, the renewal and the audit, and asks for a second factor at sign-in. cTeamCore records clocking and hours. cAssets reads equipment on the network. On the phone, mail, conversations and folders stay on the device.
Licences, sales, renewals, resellers and clients. Trial, unlock request, commissions and audit. The web asks for a second factor. The API takes a sale that starts somewhere else.
Clocking and hours for the team. Periods, people and the history operations already had. The record continues.
Inventory of physical equipment and who holds it. A program on the network reads Windows and Linux: make, model, serial and the software installed on the machine.
Mail on the phone. Passwords and messages stay on the device. Gmail and Microsoft sign in with OAuth. The rest uses IMAP or POP3, with TLS.
Closed conversations on the phone. Access is by account, and the text leaves the device encrypted. Only someone who was accepted can write.
Folders on the phone, with AES-256-GCM encryption and connections to SMB, S3, WebDAV, FTP and SFTP. A copy is removed only when the size and the MD5 prove it is the same file.
The agreement stays on the same page for both companies: the what, the price and the when. The phone shows that page.
The work session stays on the computer. The phone sees the state, replies and opens a new session through a bridge. The program that is running stays on the computer.
OUR METHOD
The working method is always the same: study the work, design it, build in versions, hand it over closed, train the people who use it, and adjust it in the first week. It holds for a platform, an app or an agent.
We sit with the person who clocks in, who sells the licence and who opens the file on a phone. We mark the repeated task, what must be recorded, and who stays accountable when an agent joins. The objective defines the screen.
Data, roles, licensing, and what happens when the network fails. If it lives in the browser or on the phone, the architecture respects that place. For an agent, we define what it may read, what it may write, and what stays with the person.
Each export — site, program or APK — continues what the previous one already did. The agent arrives only when the task is written down and the result has a place to land. The new feature sits on top of what is already in use.
Tests, Portuguese and English, and installation. The client opens the product already installed. The installer, the licence and the first account are part of that handover.
The person who will work with the agent learns to ask, to check and to stop it, on their own case. Training ends when that person can do the task on their own.
In the first week we record what the instruction did not cover. We adjust the agent, the platform or the training. The next version keeps the same name.
A platform, a licence, an Android app or an agent: study the work, architecture, version, installation, training and an adjustment in the first week.
The licence and the audit stay in cGrant. Clocking, hours and inventory stay in the client’s system. Mail, conversations and folders stay on the phone.
Anyone entering cGrant confirms their identity. Sales, renewals, trials, unlocks and commissions stay in the audit record.
In cMail, passwords and messages stay on the device. In cTalk, the text leaves encrypted. In cFolders, the encryption is AES-256-GCM.
In cBuild, the program that is running stays on the computer. The phone sees the state through a bridge.
QUESTIONS
What CodeSharper does, how we work, and how to start.
CodeSharper Solutions designs software a team uses every day: web platforms, licensing, Android apps, artificial intelligence training and AI agents. The result is an installed product, in Portuguese and in English.
Yes. Training is about the team’s real work: how to give an instruction that can be checked, how to review what the agent returns, and when the decision stays with the person. It ends with people using what was installed.
Yes. A CodeSharper agent does one concrete task, with a memory of the work, limited tools and a person accountable for the result. It reads, decides and writes in the right place, and leaves a trace of what it did.
Yes. We build Android apps to the same standard as a platform: mail that stays on the phone, closed conversations, folders with encryption, agreements between companies and a work session followed from the phone.
We study the work of the people who do it, design the data, the roles and what an agent may touch, build in versions and hand over with tests, both languages, installation and training. The first week of use fixes what the instruction did not cover.
Write to or use the form on this site. Say whether you need a platform, licensing, an Android app, training for the team or an AI agent.
It trains the people on the team, on their own work. Each person learns to write an instruction that can be checked, to review what the agent returns, and to keep the decision.
cGrant handles licences, sales and renewals. cTeamCore handles clocking and hours. cAssets handles equipment inventory. On Android: cMail, cTalk, cFolders, cAgreed and cBuild.
NEXT STEP
A platform, licensing, an Android app, training for the team or an AI agent. Write down which piece of work it is.
Or write to us at